[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Core dump (semi) update

From: Alfred M. Szmidt
Subject: Re: Core dump (semi) update
Date: Wed, 11 Feb 2004 19:47:27 +0100 (MET)

   > |   3 .reg2/23268   00000000  00000000  00000000  00000000  2**2
   > |                   CONTENTS
   > |   4 .reg2         00000000  00000000  00000000  00000000  2**2
   > |                   CONTENTS

   This is clearly wrong, it being zero.  This suggests to me that
   elfcore_grok_lwpstatus still does not have
   HAVE_LWPSTATUS_T_PR_FPREG.  Can you check that again?

Yes, it is defined and all.

,----[ somewhere in bfd/elf.c:elfcore_grok_lwpstatus() ]
|   #if defined (HAVE_LWPSTATUS_T_PR_FPREG)
| + #error "HAVE_LWPSTATUS_T_PR_FPREG is defined"
|     sect->_raw_size = sizeof (lwpstat.pr_fpreg);
|     sect->filepos = note->descpos + offsetof (lwpstatus_t, pr_fpreg);
|   #endif

And compiling it results in:

| gcc -DHAVE_CONFIG_H -I. -I../../bfd -I. -D_GNU_SOURCE -I. -I../../bfd 
-I../../bfd/../include -I../../bfd/../intl -I../intl -W -Wall 
-Wstrict-prototypes -Wmissing-prototypes -g -O2 -c ../../bfd/elf.c -o elf.o
| ../../bfd/elf.c:6654:2: #error "HAVE_LWPSTATUS_T_PR_FPREG is defined"
| ../../bfd/elf.c: In function `elfcore_write_pstatus':
| ../../bfd/elf.c:7170: warning: unused parameter `cursig'
| ../../bfd/elf.c:7171: warning: unused parameter `gregs'
| make[2]: *** [elf.lo] Error 1

   I noticed some problems with the layout crash was writing.  These
   do not explain why gdb can't grok it, I don't think.  The layout it
   was writing is correct enough to be read clearly, I believe.
   However, it was wrong it a couple of nits and I changed crash
   (exec/elfcore.c) in cvs to correct that.  Like I say, I don't think
   this fixes the gdb issue.  But it does perturb all the offsets and
   such.  So please build a fresh crash server and try the new output
   instead.  It may still have issues, but we can take it from there.

The new output didn't make gdb any more enlightened (i.e. it still
doesn't grok the core dump).


reply via email to

[Prev in Thread] Current Thread [Next in Thread]