Your message dated Sun, 22 Oct 2006 10:09:48 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#394521: gdb does not recognize core files
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
Package: gdb
Version: 6.4.90.dfsg-1
Severity: important
Hi,
when I compile the following program with gcc 4.1.1-16/binutils 2.17-3
>>> snip
int main (void)
{
int *p = 0;
return *p;
}
<<< snip
and let it core, gdb does not recognize the core file.
$ gdb a.out core
"/home/shlomme/core" is not a core dump: File format not recognized
$ readelf -a core:
ELF Header:
Magic: 7f 45 4c 46 01 01 01 00 00 00 00 00 00 00 00 00
Class: ELF32
Data: 2's complement, little endian
Version: 1 (current)
OS/ABI: UNIX - System V
ABI Version: 0
Type: CORE (Core file)
Machine: Intel 80386
Version: 0x1
Entry point address: 0x0
Start of program headers: 52 (bytes into file)
Start of section headers: 0 (bytes into file)
Flags: 0x0
Size of this header: 52 (bytes)
Size of program headers: 32 (bytes)
Number of program headers: 17
Size of section headers: 0 (bytes)
Number of section headers: 0
Section header string table index: 0
0
There are no sections in this file.
There are no sections in this file.
Program Headers:
Type Offset VirtAddr PhysAddr FileSiz MemSiz Flg Align
NOTE 0x000254 0x00000000 0x00000000 0x001d8 0x00000 0
LOAD 0x001000 0x08048000 0x00000000 0x00000 0x01000 R E 0x1000
LOAD 0x001000 0x08049000 0x00000000 0x01000 0x01000 RW 0x1000
LOAD 0x002000 0xa7e3d000 0x00000000 0x01000 0x01000 RW 0x1000
LOAD 0x003000 0xa7e3e000 0x00000000 0x00000 0x127000 R E 0x1000
LOAD 0x003000 0xa7f65000 0x00000000 0x05000 0x05000 R 0x1000
LOAD 0x008000 0xa7f6a000 0x00000000 0x02000 0x02000 RW 0x1000
LOAD 0x00a000 0xa7f6c000 0x00000000 0x03000 0x03000 RW 0x1000
LOAD 0x00d000 0xa7f82000 0x00000000 0x02000 0x02000 RW 0x1000
LOAD 0x00f000 0xa7f84000 0x00000000 0x00000 0x01000 R E 0x1000
LOAD 0x00f000 0xa7f85000 0x00000000 0x00000 0x15000 R E 0x1000
LOAD 0x00f000 0xa7f9a000 0x00000000 0x02000 0x02000 RW 0x1000
LOAD 0x011000 0xafccb000 0x00000000 0x15000 0x15000 RW 0x1000
LOAD 0x026000 0x00000000 0x00000000 0x01000 0x01000 R E 0x1000
DYNAMIC 0x0265a8 0x000005a8 0x00000000 0x00078 0x00078 R 0x4
NOTE 0x026460 0x00000460 0x00000000 0x00018 0x00018 R 0x4
GNU_EH_FRAME 0x026478 0x00000478 0x00000000 0x00024 0x00024 R 0x4
readelf: Error: Unable to read in 0x78 bytes of dynamic section
There are no relocations in this file.
There are no unwind sections in this file.
No version information found in this file.
Notes at offset 0x00000254 with length 0x000001d8:
Owner Data size Description
CORE 0x00000090 NT_PRSTATUS (prstatus structure)
CORE 0x0000007c NT_PRPSINFO (prpsinfo structure)
CORE 0x00000090 NT_AUXV (auxiliary vector)
readelf: Error: Unable to read in 0x18 bytes of notes
I admit that I don't understand anything from the output apart
from the fact that it contains some error messages...
My kernel is a vanilla 2.6.18, only unusual thing is that I is the vmsplit
patch from 2.6.18-ck1 to have 1 GiB lowmem.
best regards
Torsten
-- System Information:
Debian Release: testing/unstable
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18-shl3
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Versions of packages gdb depends on:
ii libc6 2.3.6.ds1-6 GNU C Library: Shared libraries
ii libncurses5 5.5-5 Shared libraries for terminal hand
ii libreadline5 5.1-9 GNU readline and history libraries
gdb recommends no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
On Sun, Oct 22, 2006 at 12:28:47PM +0200, Torsten Marek wrote:
> After some tinkering and comparing my kernel config against Debian's 2.6.18, I
> found out that not setting CONFIG_COMPAT_VDSO causes the core files to be
> truncated. I've set it to yes, and the core file has the expected size.
That is so very bizarre. You may want to bug the kernel folks about
it; there must be a bug involved.
--
Daniel Jacobowitz
CodeSourcery
--- End Message ---
