From: Johannes Morgenroth <morgenroth@ibr.cs.tu-bs.de>
To: buildroot@busybox.net
Subject: [Buildroot] SIGSEGV in __pthread_initialize_minimal_internal ()
Date: Thu, 06 Feb 2014 17:05:16 +0100 [thread overview]
Message-ID: <52F3B2BC.3000904@ibr.cs.tu-bs.de> (raw)
Hello.
I try to compile a DTN stack (IBR-DTN) as static binary using buildroot.
Formerly with the release 2012.02 this wasn't an issue, but since my
recent system no longer compile the old release, I tried the new one but
without any luck. Any static binary I compile exists with a SIGSEGV. To
reproduce my set-up, I pushed my repository (based on the recent master)
to github.
https://github.com/ibrdtn/buildroot.git
I used the configuration stored in the added default configuration
'ibrdtn_x86_defconfig'. So my steps are...
$ make ibrdtn_x86_defconfig
$ make
(get a coffee)
$ ./output/target/usr/sbin/dtnd --version
Segmentation fault (core dumped)
To investigate that fault, I compiled the toolchain with debug symbols
and the GDB points me to __pthread_initialize_minimal_internal ().
$ gdb --args ./output/build/ibrdtnd-0.10.2/src/dtnd
GNU gdb (GDB) 7.6.1-ubuntu
Copyright (C) 2013 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later
<http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>...
Reading symbols from ./output/build/ibrdtnd-0.10.2/src/dtnd...done.
(gdb) r
Starting program: ./output/build/ibrdtnd-0.10.2/src/dtnd
Program received signal SIGSEGV, Segmentation fault.
0x082b81f1 in __pthread_initialize_minimal_internal ()
(gdb) bt
#0 0x082b81f1 in __pthread_initialize_minimal_internal ()
#1 0x08408797 in __uClibc_init ()
#2 0x08408939 in __uClibc_main ()
#3 0x08049111 in _start ()
(gdb)
I assume this may has to do with some sort of order issues while linking
the libraries, but I am not sure and have no idea where to start with
the debugging. Any help or advice is appreciated.
Thanks!
Johannes
--
Johannes Morgenroth Institut fuer Betriebssysteme und Rechnerverbund
Tel.: +49-531-391-3249 Muehlenpfordtstrasse 23
Fax.: +49-531-391-5936 TU Braunschweig D-38106 Braunschweig
next reply other threads:[~2014-02-06 16:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-06 16:05 Johannes Morgenroth [this message]
2014-02-06 21:02 ` [Buildroot] SIGSEGV in __pthread_initialize_minimal_internal () Arnout Vandecappelle
2014-02-07 8:21 ` Johannes Morgenroth
2014-02-07 15:59 ` Johannes Morgenroth
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=52F3B2BC.3000904@ibr.cs.tu-bs.de \
--to=morgenroth@ibr.cs.tu-bs.de \
--cc=buildroot@busybox.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