Re: remote debugging and source files

Kris Warkentin
2004-08-24T18:05:42Z

Hmm...according to your info shared, you have the loader here:

0x40001460 0x40011914 No
/opt/arm-linux/gcc-3.3.3-glibc-2.3.2/arm-softfloat-linux-gnu/lib/ld-linux.so.2

so the breakpoint doesn't seem entirely unreasonable. Is there any
possibility that you have a different ld-linux.so.2 on the host and
target? Then gdb would be calculating the breakpoint incorrectly based
on the host loader. If you take a look at /usr/include/link.h, you'll
find the r_debug structure. The comments in there will help you
calculate the breakpoint by hand (look at the r_brk element) and then
you can compare it to what gdb is coming up with.

cheers,

Kris

Hinko Kocevar wrote:

> Kris Warkentin wrote:
>
>> auto-solib-add will only work properly if gdb successfully sets the
>> solib event breakpoint in the loader. Try 'maint info breakpoints'
>> and see if it's being set. You could also try setting
>> stop-on-solib-events to see if it's actually stopping. Sometimes you
>> have problems if there is a different version of the loader on host
>> and target.
>>
>
> It seems that solib events have enabled breakpoint,
>
> (gdb) maintenance info breakpoints
> Num Type Disp Enb Address What
> -2 longjmp resume keep n 0x00000000
> -3 shlib events keep y 0x4000b8d8
>
> but execution won't stop if I do
> set stop-on-solib-events 1
>
>
> regards,
> h
>