Post, Mark K wrote:
Ulrich, All,
Using GDB, I figured out that the S0C4 is coming from the path_open
routine of elf/dl-load.c in glibc. Is there any way to figure out which
assembler instructions belong to wchich lines of C source code? I don't
presume to be able to debug glibc, but at least I can try to get the
glibc developers to look at the problem.
I'd look at the output from the bt command to see what's calling glibc;
it may be something's passing some garbage.
I'm thinking back to QSAM on early OS/VS (and before), where
reading/writing an unopened file could result in 0Cx abends arounf h'48'
h'4e', near h'4800' and, on one occasiion, a loop when the instruction
down there was a bcr 15,12 and my base register was 12.
--
Cheers
John
-- spambait
[EMAIL PROTECTED] [EMAIL PROTECTED]
Tourist pics http://portgeographe.environmentaldisasters.cds.merseine.nu/
Please do not reply off-list
----------------------------------------------------------------------
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
