Skip to contentSkip to conversation

Bad core files with 2.6.19-rc2

DISCUSSION Steve Youngs 3 participants 4 messages Oct 15, 2006

lore
Share & tools
lore
#0 lore raw

gdb doesn't like any core dump file generated while running 2.6.19-rc2. If I `kill -SIGSEGV $some_app_pid' and then...

gdb some_app core

I get...

warning: Couldn't find general-purpose registers in core file. #0 0x00000000 in ?? ()

But if I gdb attach to a running process and then kill -SIGSEGV the process, it produces a normal trace without problem.

Signature · 4 lines
|---<Steve Youngs>---------------<GnuPG KeyID: A94B3003>---|
|                   Te audire no possum.                   |
|             Musa sapientum fixa est in aure.             |
|----------------------------------<[email protected]>---|
#1 lore raw
Quoted 5 lines · Steve Youngs

gdb doesn't like any core dump file generated while running 2.6.19-rc2. If I `kill -SIGSEGV $some_app_pid' and then...

gdb some_app core

Quoted 7 lines

I get...

warning: Couldn't find general-purpose registers in core file. #0 0x00000000 in ?? ()

But if I gdb attach to a running process and then kill -SIGSEGV the process, it produces a normal trace without problem.

It seems this issue should be fixed in Linus' tree now.

Can you confirm it's fixed?

TIA
Adrian

Signature · 4 lines
       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed
#2 lore raw
Quoted 13 lines · Adrian Bunk
Quoted 10 lines · Steve Youngs

gdb doesn't like any core dump file generated while running 2.6.19-rc2. If I `kill -SIGSEGV $some_app_pid' and then...

gdb some_app core

I get...

warning: Couldn't find general-purpose registers in core file. #0 0x00000000 in ?? ()

Quoted 7 lines
Quoted 2 lines

But if I gdb attach to a running process and then kill -SIGSEGV the process, it produces a normal trace without problem.

It seems this issue should be fixed in Linus' tree now.

Can you confirm it's fixed?

It should be fixed now (i.e. 26 minutes ago). Before my first fix core dump contained only some phdrs and notes, nothing else. After first fix core dump contained everything, but pieces after notes were shifted down by couple of bytes. After second fix I believe that cores are written out correctly - readelf still says that there is some zeroed note, but it seems to me like feature - older core files have this as well:

$ readelf -a core
...
Notes at offset 0x00035608 with length 0x00000018:
  Owner         Data size       Description
  Linux         0x00000004      Unknown note type: (0x00000000)

Petr Vandrovec

#3 lore raw
Quoted 10 lines · Petr Vandrovec
Quoted 7 lines · Adrian Bunk
Quoted 2 lines · Steve Youngs

warning: Couldn't find general-purpose registers in core file. #0 0x00000000 in ?? ()

It seems this issue should be fixed in Linus' tree now.

Can you confirm it's fixed?

It should be fixed now

Yes, it is. Thank you very much.

Signature · 4 lines
|---<Steve Youngs>---------------<GnuPG KeyID: A94B3003>---|
|                   Te audire no possum.                   |
|             Musa sapientum fixa est in aure.             |
|----------------------------------<[email protected]>---|