[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Libunwind-devel] mips implementation of libunwind SEGV Faulting
From: |
John Knight |
Subject: |
Re: [Libunwind-devel] mips implementation of libunwind SEGV Faulting |
Date: |
Mon, 30 Jan 2017 18:12:03 +0000 |
Hi Dave,
I don't have a backtrace for the segv... the backtrace is what we want to use
libunwind for! :-)
I will try versions 1.1 and 1.0 and see what happens with those. It may take
me awhile as my time for this effort is essentially on the back burner. I will
let you know.
John
-----Original Message-----
From: Dave Watson [mailto:address@hidden
Sent: Friday, January 27, 2017 8:09 AM
To: John Knight
Cc: address@hidden
Subject: Re: [Libunwind-devel] mips implementation of libunwind SEGV Faulting
On 01/27/17 02:17 AM, John Knight wrote:
> Thanks for the missing .h file for the mips. With that file, I was able to
> successfully build the libunwind library files for mips. I have verified
> that the libraries built are all MIPS. However, when I go to test the
> backtrace with the same application as I had tested successfully with arm, it
> causes the app to SEGV fault (signal 11). Was the mips implementation
> validated with the 1.2 release? I am running GNU/linux 2.6.36. I used -g
> -O0 options when compiling libraries and the app, which should turn off all
> optimization.
>
> I have attached a copy of the app's backtrace.c which I am using to
do the backtrace using libunwind.
Do you have a backtrace from the segv, using gdb or something?
> I am interested in knowing what you think? I would like to hear if anyone
> else is seeing issue with the Mips implementation?
I don't have a mips machine at the moment (somewhere on my list of
things to do). Do v1.1 or v1.0 work for you? There were only a
small handful of mips-specific diffs between versions, should be easy to bisect
if so.
__________________________________________________________________ Confidential
This e-mail and any files transmitted with it are the property of Belkin
International, Inc. and/or its affiliates, are confidential, and are intended
solely for the use of the individual or entity to whom this e-mail is
addressed. If you are not one of the named recipients or otherwise have reason
to believe that you have received this e-mail in error, please notify the
sender and delete this message immediately from your computer. Any other use,
retention, dissemination, forwarding, printing or copying of this e-mail is
strictly prohibited. Pour la version française:
http://www.belkin.com/email-notice/French.html Für die deutsche Übersetzung:
http://www.belkin.com/email-notice/German.html
__________________________________________________________________