From: Sven Neumann <s.neumann@raumfeld.com>
To: buildroot@busybox.net
Subject: [Buildroot] Segmentation faults after gcc update
Date: Tue, 04 Oct 2011 11:20:47 +0200 [thread overview]
Message-ID: <1317720237.2409.0.camel@sven> (raw)
In-Reply-To: <20110930215915.3d7fad80@skate>
On Fri, 2011-09-30 at 21:59 +0200, Thomas Petazzoni wrote:
> Le Fri, 30 Sep 2011 11:06:46 +0200,
> Sven Neumann <s.neumann@raumfeld.com> a ?crit :
>
> > > 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.
> >
> > I have now added some debug output to _dl_get_tls_static_info() and
> > related functions and from that I can tell that gdb is wrong here. The
> > code does definitely not crash in _dl_get_tls_static_info() and not in
> > _dl_update_slotinfo() either.
> >
> > Now I am somewhat stuck. Any further ideas on how I could tackle this
> > problem?
>
> I guess the whole stack trace is stupid, because I don't see how
> hasmntopt() can end up calling sched_get_priority_max():
>
> char *hasmntopt(const struct mntent *mnt, const char *opt)
> {
> return strstr(mnt->mnt_opts, opt);
> }
>
> Maybe you should raise the issue on the uClibc mailing list?
I've opened https://bugs.busybox.net/show_bug.cgi?id=4291 for it and
will also ask on the mailing list in case that the bug report won't get
any attention.
Thanks,
Sven
next prev parent reply other threads:[~2011-10-04 9:20 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
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 [this message]
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=1317720237.2409.0.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 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.