On Mon, 2007-01-22 at 09:25 -0500, Mark Post wrote: > No, that wasn't it. I had to rebuild glibc anyway, so I wrote everything to > a log (as usual). No truncation messages, but the problem still exists. > > One thing I didn't think to look at before are the several calls to __xstat > earlier in the gdb run. Those all seem to go fine. When I look at what > routine is calling it, it's __libc_csu_fini. When I disassemble that, the > call looks like this: > 0x0000000080064ad0 <__libc_csu_fini+148>: brasl %r14,0x8000aec4 > <[EMAIL PROTECTED]> > > You can see that the branch is going to [EMAIL PROTECTED] > > What I find odd is that when the breakpoint trips, it says: > Breakpoint 1, 0x00000100002fe2dc in _xstat () from /lib64/libc.so.6 > > So, the difference between success and failure is > 0x8000aec4 versus 0x1008000aec4
Do a "readelf -a" on the object that contains auth_md5_valid and take a look at the relocations that are applied to the function. The code snippet above does not match the code snippet that contains the broken brasl. The last tree digits of the address have to match. I think you are looking at a different object. -- blue skies, Martin. Martin Schwidefsky Linux for zSeries Development & Services IBM Deutschland Entwicklung GmbH "Reality continues to ruin my life." - Calvin. ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
