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. _______________________________________________ Libunwind-devel mailing list [email protected] https://lists.nongnu.org/mailman/listinfo/libunwind-devel
