This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

Setting up gdb-7.1 to inspect core dump from evmdm365

Expert 2315 points

I have seen on TI training video for OMAP that the following setting are done before using the debugger:

(gdb) set solib-absolute-prefix /home/gvi/workdir/filesys

(gdb) set solib-search-path /home/gvi/workdir/filesys/usr/lib;/home/gvi/workdir/filesys/lib

When I load my core dump files I get different results when I inspect the core dump files with the settings and without the settings.  My problem is that the results from the core dump makes more sense without doing these settings, in other words, it is more applicable to my application code than with the settings done where it just spits out the following: #0 0x400b8060 in strcat () from /lib/libc.so.6 for htread 1 or for thread 2 is gives: #0 0x0000a398 in display_frame (id=3 '\003', etr_buffer=0x41280000) at fbdev_loopback.c:1418.

Please indicate if you need more info from core inspection to help on this.  What should the correct setting be?

Thanks, Jinh T.