From: Sven Neumann <s.neumann@raumfeld.com>
To: buildroot@busybox.net
Subject: [Buildroot] Segmentation faults after gcc update
Date: Wed, 28 Sep 2011 16:44:32 +0200 [thread overview]
Message-ID: <1317221262.8481.4.camel@sven> (raw)
In-Reply-To: <20110927233506.55cb52a2@skate>
Hi,
On Tue, 2011-09-27 at 23:35 +0200, Thomas Petazzoni wrote:
> * What does a gdb session says for the execution of one of those
> binaries ?
OK, so I had to compile a gdb for the target first. Here's the result:
# gdb dbus-daemon
GNU gdb (GDB) 7.1
Copyright (C) 2010 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 "arm-unknown-linux-uclibcgnueabi".
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>...
Reading symbols from /usr/bin/dbus-daemon...(no debugging symbols found)...done.
(gdb) r
Starting program: /usr/bin/dbus-daemon
warning: Unable to find libthread_db matching inferior's thread library, thread debugging will not be available.
warning: Unable to find libthread_db matching inferior's thread library, thread debugging will not be available.
warning: Unable to find libthread_db matching inferior's thread library, thread debugging will not be available.
warning: Unable to find libthread_db matching inferior's thread library, thread debugging will not be available.
warning: Unable to find libthread_db matching inferior's thread library, thread debugging will not be available.
warning: Unable to find libthread_db matching inferior's thread library, thread debugging will not be available.
Program received signal SIGSEGV, Segmentation fault.
0x40086254 in _dl_get_tls_static_info () from /lib/ld-uClibc.so.0
(gdb) bt
#0 0x40086254 in _dl_get_tls_static_info () from /lib/ld-uClibc.so.0
#1 0x40087064 in _dl_update_slotinfo () from /lib/ld-uClibc.so.0
#2 0x401584a0 in sched_get_priority_max () from /lib/libc.so.0
#3 0x4015f040 in hasmntopt () from /lib/libc.so.0
#4 0x4015f040 in hasmntopt () from /lib/libc.so.0
Backtrace stopped: previous frame identical to this frame (corrupt stack?)
(gdb)
I don't quite understand why libthread_db is not found as I did enable
BR2_PTHREAD_DEBUG for this build and recompiled everything. Anyway, I
tried gdb on a different (crashing) binary and it crashes in
_dl_get_tls_static_info() as well.
Regards,
Sven
next prev parent reply other threads:[~2011-09-28 14:44 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-27 8:04 [Buildroot] Segmentation faults after gcc update Sven Neumann
2011-09-27 21:35 ` Thomas Petazzoni
2011-09-28 8:57 ` Sven Neumann
2011-09-28 14:44 ` Sven Neumann [this message]
2011-09-30 9:06 ` Sven Neumann
2011-09-30 19:59 ` Thomas Petazzoni
2011-09-30 20:35 ` Thomas Petazzoni
2012-02-20 10:37 ` Sven Neumann
2012-02-20 16:55 ` Thomas Petazzoni
2011-10-04 9:20 ` Sven Neumann
2011-09-27 21:36 ` Thomas Petazzoni
2011-09-28 9:18 ` Sven Neumann
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=1317221262.8481.4.camel@sven \
--to=s.neumann@raumfeld.com \
--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