From: Adrian Bunk <bunk@stusta.de>
To: linux-kernel@vger.kernel.org
Cc: Petr Vandrovec <petr@vandrovec.name>
Subject: Re: Bad core files with 2.6.19-rc2
Date: Sun, 15 Oct 2006 20:42:17 +0200 [thread overview]
Message-ID: <20061015184217.GZ30596@stusta.de> (raw)
In-Reply-To: <microsoft-free.87mz7yjnm2.fsf@youngs.au.com>
On Sun, Oct 15, 2006 at 12:53:41PM +1000, Steve Youngs wrote:
> 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.
It seems this issue should be fixed in Linus' tree now.
Can you confirm it's fixed?
TIA
Adrian
--
"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
next prev parent reply other threads:[~2006-10-15 18:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-15 2:53 Bad core files with 2.6.19-rc2 Steve Youngs
2006-10-15 18:42 ` Adrian Bunk [this message]
2006-10-15 19:24 ` Petr Vandrovec
2006-10-15 22:15 ` Steve Youngs
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20061015184217.GZ30596@stusta.de \
--to=bunk@stusta.de \
--cc=linux-kernel@vger.kernel.org \
--cc=petr@vandrovec.name \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox