From: Johannes Morgenroth <morgenroth@ibr.cs.tu-bs.de>
To: buildroot@busybox.net
Subject: [Buildroot] SIGSEGV in __pthread_initialize_minimal_internal ()
Date: Fri, 07 Feb 2014 16:59:41 +0100 [thread overview]
Message-ID: <52F502ED.6000902@ibr.cs.tu-bs.de> (raw)
In-Reply-To: <52F3B2BC.3000904@ibr.cs.tu-bs.de>
I do not know why, but disabling SSP (stack protection) allows to
generate working binaries again.
Maybe now anyone can tell me why that is an issue?
Kind regards,
Johannes Morgenroth
Am 06.02.2014 17:05, schrieb Johannes Morgenroth:
> $ 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)
--
Johannes Morgenroth Institut fuer Betriebssysteme und Rechnerverbund
Tel.: +49-531-391-3249 Muehlenpfordtstrasse 23
Fax.: +49-531-391-5936 TU Braunschweig D-38106 Braunschweig
prev parent reply other threads:[~2014-02-07 15:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-06 16:05 [Buildroot] SIGSEGV in __pthread_initialize_minimal_internal () Johannes Morgenroth
2014-02-06 21:02 ` Arnout Vandecappelle
2014-02-07 8:21 ` Johannes Morgenroth
2014-02-07 15:59 ` Johannes Morgenroth [this message]
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=52F502ED.6000902@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