From: "Ulrich Windl" <ulrich.windl@rz.uni-regensburg.de>
Organization: Universitaet Regensburg, Klinikum
To: Al Viro <viro@ftp.linux.org.uk>
Date: Wed, 12 Sep 2007 08:35:57 +0200
MIME-Version: 1.0
Subject: Re: Socket-related problem in x86_64 Kernel (2.6.16.53-0.8-smp)?
CC: Eric Dumazet <dada1@cosmosbay.com>, linux-kernel@vger.kernel.org
Message-ID: <46E7A4ED.5971.189F731B@Ulrich.Windl.rkdvmks1.ngate.uni-regensburg.de>
In-reply-to: <20070911160432.GA8181@ftp.linux.org.uk>
References: <46E6D660.16004.15789926@Ulrich.Windl.rkdvmks1.ngate.uni-regensburg.de>
Content-type: text/plain; charset=US-ASCII
Content-transfer-encoding: 7BIT
Content-description: Mail message body
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1111
Lines: 27

On 11 Sep 2007 at 17:04, Al Viro wrote:

> 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.

Ok, but why is the message there at all? I think in Windows/XP the offending code 
and the registers are shown in such occasions. I'd say either drop the message, or 
improve it. It's also difficult to find the code after the program is gone due to 
mapping of shared libraries. I managed to get a core dump of the application 
however, and I did modify some code. I'll report once I have results.

Maybe it's "mea culpa" for my program, but powersaved and slapd are still to be 
examined.

Regards,
Ulrich

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/