From: Al Viro <viro@ftp.linux.org.uk>
To: Ulrich Windl <ulrich.windl@rz.uni-regensburg.de>
Cc: Eric Dumazet <dada1@cosmosbay.com>, linux-kernel@vger.kernel.org
Subject: Re: Socket-related problem in x86_64 Kernel (2.6.16.53-0.8-smp)?
Date: Tue, 11 Sep 2007 17:04:32 +0100 [thread overview]
Message-ID: <20070911160432.GA8181@ftp.linux.org.uk> (raw)
In-Reply-To: <46E6D660.16004.15789926@Ulrich.Windl.rkdvmks1.ngate.uni-regensburg.de>
On Tue, Sep 11, 2007 at 05:54:38PM +0200, Ulrich Windl wrote:
> If not, any clues on debugging/tracing? There's a
> /usr/src/linux/Documentation/oops-tracing.txt, but no "segfault-tracing".
That would be because it has fsck-all to do with the kernel. Get the
coredump, then use gdb to deal with it.
next prev parent reply other threads:[~2007-09-11 16:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-11 9:30 Ulrich Windl
2007-09-11 13:01 ` Eric Dumazet
2007-09-11 15:15 ` Ulrich Windl
2007-09-11 15:57 ` Eric Dumazet
2007-09-11 15:54 ` Ulrich Windl
2007-09-11 16:04 ` Al Viro [this message]
2007-09-12 6:35 ` Ulrich Windl
2007-09-11 16:14 ` Jan Engelhardt
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=20070911160432.GA8181@ftp.linux.org.uk \
--to=viro@ftp.linux.org.uk \
--cc=dada1@cosmosbay.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ulrich.windl@rz.uni-regensburg.de \
/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
all inboxes | Powered by JetHome®