From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] core file
Date: Thu, 15 Mar 2012 16:52:58 +0100 [thread overview]
Message-ID: <20120315165258.3aec835e@skate> (raw)
In-Reply-To: <486BF3F63CBA4E08B41FE14F46199C39@JohanW7>
Le Thu, 15 Mar 2012 15:36:35 +0100,
"Sagaert Johan" <sagaert.johan@skynet.be> a ?crit :
> This is the result from a run with no debug symbols
Yeah, but then it's useless. You should build curl and libcurl with
debugging symbols, and the C library without. But it's unfortunately
not easy to do with Buildroot.
> Also tested using ARM926t instead of the Generic Arm, but this makes no difference. (arm926t = Thumb ?)
The T is to say that Thumb is supported, but unless you specify -mthumb
in the flags, it's still ARM code that gets generated.
> Since libdl is the last one, could this one be the one causing the segfault ?
No, it's just the last shared library that gets loaded, nothing to do
with the reason of the crash.
> Core was generated by `curl'.
> Program terminated with signal 11, Segmentation fault.
> #0 0x00000000 in ?? ()
So it crashes that early? Strange.
Can you put your root filesystem image somewhere online?
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2012-03-15 15:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <DC8F7388218A402C9FEADA4D9CC577B3@JohanW7>
2012-03-15 7:00 ` [Buildroot] core file Thomas Petazzoni
2012-03-15 12:17 ` Sagaert Johan
2012-03-15 13:19 ` Thomas Petazzoni
2012-03-15 14:36 ` Sagaert Johan
2012-03-15 15:52 ` Thomas Petazzoni [this message]
2012-03-15 22:46 ` Arnout Vandecappelle
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=20120315165258.3aec835e@skate \
--to=thomas.petazzoni@free-electrons.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