From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] core file
Date: Thu, 15 Mar 2012 23:46:26 +0100 [thread overview]
Message-ID: <201203152346.27014.arnout@mind.be> (raw)
In-Reply-To: <20120315141929.1b885c74@skate>
On Thursday 15 March 2012 14:19:29 Thomas Petazzoni wrote:
> And you have built it with debugging symbols it seems, so its size is
> way too big to load on your target. Either use cross-gdb+gdbserver, or
> don't compile the uClibc with debugging symbols.
cross-gdb with or without gdbserver is really the way to go. Then you
don't need to compile with debug symbols. But I guess Johan would like
to get some explanation how to do that.
Without gdbserver:
On the target, enable core files with 'ulimit -c 0' and run curl.
You should get a core file in the current directory.
Copy the core file to the build host.
Go to the source directory of curl. Run
../../host/usr/bin/arm*gdb src/curl <corefile>
Now you can look at the backtrace in the debugger, it shows the
source as well.
With gdbserver:
On the target, run
gdbserver any:8888 curl
On the host, run gdb in the curl source directory like above.
../../host/usr/bin/arm*gdb src/curl
gdb> set target <ipaddr>:8888
gdb> continue
Now the program runs up to the segmentation fault.
Regards,
Arnout
--
Arnout Vandecappelle arnout at mind be
Senior Embedded Software Architect +32-16-286540
Essensium/Mind http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint: 7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F
prev parent reply other threads:[~2012-03-15 22:46 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
2012-03-15 22:46 ` Arnout Vandecappelle [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=201203152346.27014.arnout@mind.be \
--to=arnout@mind.be \
--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