Bad core files with 2.6.19-rc2
- From: Steve Youngs <steve@xxxxxxxxxxxxx>
- Date: Sun, 15 Oct 2006 12:53:41 +1000
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.
--
|---<Steve Youngs>---------------<GnuPG KeyID: A94B3003>---|
| Te audire no possum. |
| Musa sapientum fixa est in aure. |
|----------------------------------<steve@xxxxxxxxxxxxx>---|
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
- Follow-Ups:
- Re: Bad core files with 2.6.19-rc2
- From: Adrian Bunk
- Re: Bad core files with 2.6.19-rc2
- Prev by Date: [PATCH 19-rc2] Fix misc Kconfig typos
- Next by Date: Re: [PATCH 1/2] [PCI] Check that MWI bit really did get set
- Previous by thread: [PATCH 19-rc2] Fix misc Kconfig typos
- Next by thread: Re: Bad core files with 2.6.19-rc2
- Index(es):
Relevant Pages
|
