From: Jeff Dike <jdike@addtoit.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: User-mode Linux Kernel Development
<user-mode-linux-devel@lists.sourceforge.net>
Subject: Re: The Story Continues (was: Re: [uml-devel] Re: pthreads?)
Date: Fri, 10 Oct 2003 21:48:51 -0400 [thread overview]
Message-ID: <200310110148.h9B1mp4f006913@ccure.karaya.com> (raw)
In-Reply-To: Your message of "Tue, 07 Oct 2003 17:51:20 +0200." <Pine.GSO.4.21.0310071735310.2653-100000@waterleaf.sonytel.be>
geert@linux-m68k.org said:
> Kernel panic: Segfault with no mm
> when GTK calls my expose handler and I call gdk_draw_indexed_image()
> to update the window contents.
>
> If I run the image under gdb, it crashes even earlier in gtk_init()
> with
>
> Kernel panic: Kernel mode signal 5
The mere act of running it under gdb causes this, or did you set some
breakpoints?
As an arch maintainer, I bet you're aware of this, but somehow, UML is getting
a SIGTRAP that gdb isn't expecting. Setting breakpoints in tricky ways can
do this.
> Anyone with a clue how to investigate such behavior? Thx!
You might stick an infinite loop after the panic string is printed. Then
attach gdb to UML then. At least you'll get a stack trace from the panic.
Jeff
-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
SourceForge.net hosts over 70,000 Open Source Projects.
See the people who have HELPED US provide better services:
Click here: http://sourceforge.net/supporters.php
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
next prev parent reply other threads:[~2003-10-11 1:46 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-11 15:54 [uml-devel] pthreads? Geert Uytterhoeven
2003-09-11 17:55 ` Jeff Dike
2003-09-12 8:52 ` [uml-devel] pthreads? Gerd Knorr
2003-09-12 9:07 ` Geert Uytterhoeven
2003-09-12 11:08 ` Gerd Knorr
2003-09-12 11:18 ` Geert Uytterhoeven
2003-09-12 12:15 ` Gerd Knorr
2003-09-12 12:17 ` Geert Uytterhoeven
2003-09-12 11:18 ` Henrik Nordstrom
2003-09-12 16:28 ` Jeff Dike
2003-09-12 22:25 ` Henrik Nordstrom
2003-09-13 18:53 ` Jeff Dike
2003-09-13 21:01 ` Henrik Nordstrom
2003-09-13 15:24 ` Geert Uytterhoeven
2003-09-13 18:54 ` Jeff Dike
2003-09-15 6:57 ` Geert Uytterhoeven
2003-09-15 9:19 ` Henrik Nordstrom
2003-09-15 9:28 ` Geert Uytterhoeven
2003-09-15 10:51 ` Henrik Nordstrom
2003-09-16 18:44 ` BlaisorBlade
2003-10-02 9:20 ` Jan Hudec
2003-10-02 9:08 ` Jan Hudec
2003-10-02 9:24 ` Geert Uytterhoeven
2003-10-02 9:31 ` Jan Hudec
[not found] ` <Pine.GSO.4.21.0310021146500.8567-100000@vervain.sonytel.be>
2003-10-02 13:52 ` Jan Hudec
2003-10-02 14:28 ` Geert Uytterhoeven
2003-10-02 14:42 ` Jan Hudec
2003-10-07 15:51 ` The Story Continues (was: Re: [uml-devel] Re: pthreads?) Geert Uytterhoeven
2003-10-11 1:48 ` Jeff Dike [this message]
2003-10-11 8:39 ` Geert Uytterhoeven
2003-10-12 9:53 ` Geert Uytterhoeven
2003-10-06 13:29 ` [uml-devel] Re: pthreads? BlaisorBlade
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=200310110148.h9B1mp4f006913@ccure.karaya.com \
--to=jdike@addtoit.com \
--cc=geert@linux-m68k.org \
--cc=user-mode-linux-devel@lists.sourceforge.net \
/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