From: "Michael Ralston" <ralston@stral.net>
To: user-mode-linux-devel@lists.sourceforge.net
Cc: 'Jeff Dike' <jdike@addtoit.com>
Subject: RE: [uml-devel] Compiling UML 2.6.8.1 with Static Linking results in segfault
Date: Wed, 8 Sep 2004 10:04:40 +1000 [thread overview]
Message-ID: <E1C4pxK-0008QL-3Q@sc8-sf-mx2.sourceforge.net> (raw)
In-Reply-To:
[-- Attachment #1: Type: text/plain, Size: 1660 bytes --]
Hey, the core is 20k gzipped :)
Michael
> -----Original Message-----
> From: Michael Ralston [mailto:ralston@stral.net]
> Sent: Wednesday, 8 September 2004 9:58 AM
> To: 'user-mode-linux-devel@lists.sourceforge.net'
> Cc: 'Jeff Dike'
> Subject: RE: [uml-devel] Compiling UML 2.6.8.1 with Static
> Linking results in segfault
>
> The core is 483k, want me to email that just to you (not the
> list), or is the gdb output below pretty conclusive?
>
> I'm running this on a 2.6.8.1 host with SKAS3-2.6.7-v1 patch,
> and as I said libc6-2.3.2, so it's prolly another one of
> those lovely NPTL/TLS issues.
>
> The Config options which are set:
> # CONFIG_MODE_TT is not set
> CONFIG_STATIC_LINK=y
> CONFIG_MODE_SKAS=y
>
> If I disable STATIC_LINK then it runs fine...
>
>
> (gdb) run
> Starting program: /uml/linux
>
> Program received signal SIGSEGV, Segmentation fault.
> 0x08191800 in __libc_setup_tls () at swab.h:134
> 134 swab.h: No such file or directory.
> in swab.h
>
>
>
> > -----Original Message-----
> > From: Jeff Dike [mailto:jdike@addtoit.com]
> > Sent: Wednesday, 8 September 2004 10:18 AM
> > 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
> >
> > ralston@stral.net said:
> > > Can I provide any further info or is this a known problem?
> >
> > Get a core, and get a stack trace from it?
> >
> > Jeff
> >
> >
---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.752 / Virus Database: 503 - Release Date: 3/09/2004
[-- Attachment #2: core.gz --]
[-- Type: application/octet-stream, Size: 20991 bytes --]
next reply other threads:[~2004-09-08 0:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-08 0:04 Michael Ralston [this message]
[not found] <200409080004.i8804KC20166@lakshmi.solana.com>
2004-09-09 0:43 ` [uml-devel] Compiling UML 2.6.8.1 with Static Linking results in segfault Jeff Dike
2004-09-09 4:51 ` Michael Ralston
2004-09-09 18:20 ` BlaisorBlade
[not found] <200409072357.i87NvPC20122@lakshmi.solana.com>
2004-09-09 0:42 ` Jeff Dike
-- 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=E1C4pxK-0008QL-3Q@sc8-sf-mx2.sourceforge.net \
--to=ralston@stral.net \
--cc=jdike@addtoit.com \
--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.