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 [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
