From: Daniel Jacobowitz <drow@false.org>
To: Sergei Poselenov <sposelenov@emcraft.com>
Cc: gdb@sources.redhat.com
Subject: Re: Problem reading corefiles on ARM
Date: Thu, 07 Aug 2008 13:44:00 -0000 [thread overview]
Message-ID: <20080807134414.GA11515@caradoc.them.org> (raw)
In-Reply-To: <489AC07E.2020603@emcraft.com>
On Thu, Aug 07, 2008 at 01:29:34PM +0400, Sergei Poselenov wrote:
> This time, the core was generated by "kill -SIGSEGV".
>
> Could it be a kernel bug?
Yes, that's certainly a kernel bug. I believe it is fixed in current
kernel.org kernels, but I'm not sure; it breaks periodically.
--
Daniel Jacobowitz
CodeSourcery
prev parent reply other threads:[~2008-08-07 13:44 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-06 15:20 Sergei Poselenov
2008-08-06 15:28 ` Daniel Jacobowitz
2008-08-06 15:45 ` Mark Kettenis
2008-08-06 15:51 ` Daniel Jacobowitz
2008-08-06 16:02 ` Paul Koning
2008-08-06 17:10 ` Joe Buck
2008-08-06 17:39 ` Paul Koning
2008-08-06 17:52 ` Joe Buck
2008-08-06 18:11 ` Paul Koning
2008-08-06 21:39 ` Andreas Schwab
2008-08-06 21:58 ` Joe Buck
2008-08-07 13:30 ` Paul Koning
2008-08-07 16:56 ` Joe Buck
2008-08-07 17:29 ` Paul Koning
2008-08-07 9:30 ` Sergei Poselenov
2008-08-07 13:44 ` Daniel Jacobowitz [this message]
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=20080807134414.GA11515@caradoc.them.org \
--to=drow@false.org \
--cc=gdb@sources.redhat.com \
--cc=sposelenov@emcraft.com \
/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