From: Maxime Ripard <maxime.ripard@free-electrons.com>
To: buildroot@busybox.net, crossgcc@sourceware.org
Subject: ltrace hangings
Date: Tue, 28 Feb 2012 16:48:00 -0000 [thread overview]
Message-ID: <4F4D052C.3030608@free-electrons.com> (raw)
Hi everyone,
I'm having a hard time here using ltrace with buildroot or crosstool-ng.
Basically, with a crosstool-NG 1.13.4, with the sample
arm-unknown-linux-gnueabi (so uclibc 0.9.30.2), I get :
__uClibc_main(52956, 2, 0xbec42db4, 47280, 521292
and it hangs.
Same thing with a toolchain built by buildroot and with uclibc 0.9.32.
Finally, I tried still with buildroot, but using the latest codebench
glibc toolchain, I get:
# ltrace cat /proc/self/cmdline
__libc_start_main(53812, 2, 0xbefeedb4, 518624, 518824
Is it a wild guess to think that ltrace 0.5.3 is buggy, or am I doing
something wrong ?
--
Maxime Ripard, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
--
For unsubscribe information see http://sourceware.org/lists.html#faq
next reply other threads:[~2012-02-28 16:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-28 16:48 Maxime Ripard [this message]
2012-02-28 22:34 ` Yann E. MORIN
2012-02-29 13:04 ` Maxime Ripard
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=4F4D052C.3030608@free-electrons.com \
--to=maxime.ripard@free-electrons.com \
--cc=buildroot@busybox.net \
--cc=crossgcc@sourceware.org \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).