Description of problem:

<foo> elena: btw, somebody broke gdb since it is now unable to debug
ld.so.  probably happened as part of making pies work
<elena> foo: where? rhel3/rhel4/both? platforms?
<elena> foo: when. pie has been in there since last summer
<foo> elena: fc3 and therefore probably rhel4.  haven't tested rhel3
<elena> foo: there was a bug report for that on ppc
<foo> elena: well, there have been more changes.  I think it's not too
long.
<foo> elena: anyway, it makes debugging glibc extremely difficult at times
<elena> foo: ok, i have seen weird bug reports lately. Some section
reordering and some abi changes broke gdb on ppc, but i wonder about
other platforms
<foo> elena: this is x86.  if you just build glibc, then start gdb on
ld.so, try putting a breakpoint in "dl_main".
<foo> elena: gdb will add the breakpoint but will never stop
<foo> elena: ld.so is a special program.  it's relocatable, but it's
not a PIE
<foo> elena: the address looks perfectly fine
<foo> (gdb) b dl_main
<foo> Breakpoint 1 at 0x1592: file rtld.c, line 812.
<foo> (gdb) r --library-path . /bin/cat
<foo> Starting program:
/home/drepper-local/glibc-build/ld-20041026/elf/ld.so --library-path .
/bin/cat
<foo> Breakpoint 1 at 0xf6feb592: file rtld.c, line 812.
<elena> foo: but it is not reached, which I found odd, or more likely
gdb doesn't recognize the signal as at a valid breakpoint location
<foo> f6fea000-f7000000 r-xp 00000000 03:08 2413888   
/home/drepper-local/glibc-build/ld-20041026/elf/ld.so
<foo> elena: and 0xf6feb592-0xf6fea000==0x1592
<elena> ah
<foo> elena: and in ld.so:
<foo> 00001580 <dl_main>:
<foo>     1580:       55                      push   %ebp
<foo>     1581:       89 e5                   mov    %esp,%ebp
<foo>     1583:       57                      push   %edi
<foo>     1584:       56                      push   %esi
<foo>     1585:       53                      push   %ebx
<foo>     1586:       e8 00 00 00 00          call   158b <dl_main+0xb>
<foo>     158b:       5b                      pop    %ebx
<foo>     158c:       81 c3 69 5a 01 00       add    $0x15a69,%ebx
<foo>     1592:       8d 83 18 9a fe ff       lea 0xfffe9a18(%ebx),%eax
<foo> elena: so, gdb found the end of the prologue
<elena> foo: so the reloc looks correct
<foo> elena: yep
<elena> i wonder if the internal gdb breakpoint structure is just not
updated to reflect the relocated addr, so when it stops there it
doesn't find any bp to match it with

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info: