linux-um archives
 help / color / mirror / Atom feed
From: "Michael Ralston" <ralston@stral.net>
To: ralston@stral.net, user-mode-linux-devel@lists.sourceforge.net
Cc: 'Jeff Dike' <jdike@addtoit.com>
Subject: [uml-devel] Compiling UML 2.6.8.1 w/Static Link... 2.4.26 also segfaults... Damn nptl
Date: Wed, 8 Sep 2004 14:20:30 +1000	[thread overview]
Message-ID: <E1C4twr-0006wN-AA@sc8-sf-mx2.sourceforge.net> (raw)
In-Reply-To: 

Just tried out 2.4.26-3 with the static linked skas option... Its segfaults
too

Michael

> -----Original Message-----
> From: Michael Ralston [mailto:ralston@stral.net] 
> Sent: Wednesday, 8 September 2004 10:05 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 
> 
> 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
>  
>   
> 



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

                 reply	other threads:[~2004-09-08  4:20 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=E1C4twr-0006wN-AA@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox