libunwind-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Libunwind-devel] mips implementation of libunwind SEGV Faulting


From: John Knight
Subject: [Libunwind-devel] mips implementation of libunwind SEGV Faulting
Date: Fri, 27 Jan 2017 02:17:37 +0000

Hi Dave,

 

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.

 

I am interested in knowing what you think?  I would like to hear if anyone else is seeing issue with the Mips implementation?

 

Thanks,

 

John Knight

address@hidden

__________________________________________________________________ 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 __________________________________________________________________

Attachment: backtrace.c
Description: backtrace.c


reply via email to

[Prev in Thread] Current Thread [Next in Thread]