[arm-gnu] Issue with gdb 7.0 backtrace

[Carlos O'Donell]

[trimming CC].

On 12/20/2011 4:31 AM, solmac john wrote:
> As we know, generally, we run bt command in gdb, gdb show the seg fault location in last backtrace.
>  
> I found one strange behaviour If i run  bt command in gdb, at that itme, gdb didn’t show the segment  fault location in backtrace by default.

That's normal, `bt' shows only the backtrace for the last active thread.

You must run `thread apply backtrace' (or some shortcut form) to get a backtrace of *all* threads to see which one most likely faulted.

> Can some one tell the reason 
> and is this expected in SMP
> 
> warning: Unable to find dynamic linker.
> GDB will be unable to debug shared library initializers
> and track explicitly loaded dynamic code.

I assume you are going remote debug.

Until you fix the "warning: ..." you're going to have problems debugging anything with threads.

The warning indicates that gdb, and the target do not agree about the libraries they are using for debugging.

You must keep the target in sync with the runtimes you use for debugging, otherwise debugging is unreliable.

Cheers,
Carlos.
-- 
Carlos O'Donell
Mentor Graphics / CodeSourcery
carlos at codesourcery.com
+1 (613) 963 1026