From: Jeff Dike <jdike@addtoit.com>
To: ralston@stral.net
Cc: user-mode-linux-devel@lists.sourceforge.net
Subject: Re: [uml-devel] Compiling UML 2.6.8.1 with Static Linking results in segfault
Date: Wed, 08 Sep 2004 20:43:51 -0400 [thread overview]
Message-ID: <200409090043.i890hpBP016311@ccure.user-mode-linux.org> (raw)
In-Reply-To: Your message of "Wed, 08 Sep 2004 10:04:40 +1000." <200409080004.i8804KC20166@lakshmi.solana.com>
ralston@stral.net said:
> Hey, the core is 20k gzipped :)
And the core is useless without the binary that produced it. In any case,
it's probably a lot easier for you to type 'bt' at gdb and send that rather
than compressing a core file and binary and sending them.
Jeff
-------------------------------------------------------
This SF.Net email is sponsored by BEA Weblogic Workshop
FREE Java Enterprise J2EE developer tools!
Get your free copy of BEA WebLogic Workshop 8.1 today.
http://ads.osdn.com/?ad_id=5047&alloc_id=10808&op=click
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
next parent reply other threads:[~2004-09-08 23:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200409080004.i8804KC20166@lakshmi.solana.com>
2004-09-09 0:43 ` Jeff Dike [this message]
2004-09-09 4:51 ` [uml-devel] Compiling UML 2.6.8.1 with Static Linking results in segfault Michael Ralston
2004-09-09 18:20 ` BlaisorBlade
[not found] <200409072357.i87NvPC20122@lakshmi.solana.com>
2004-09-09 0:42 ` Jeff Dike
2004-09-08 0:04 Michael Ralston
-- strict thread matches above, loose matches on Subject: below --
2004-08-19 3:00 [uml-devel] uml-patch-2.6.7-2 Jeff Dike
2004-09-07 21:16 ` [uml-devel] Compiling UML 2.6.8.1 with Static Linking results in segfault Michael Ralston
2004-09-08 0:18 ` Jeff Dike
2004-09-07 23:57 ` Michael Ralston
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=200409090043.i890hpBP016311@ccure.user-mode-linux.org \
--to=jdike@addtoit.com \
--cc=ralston@stral.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.