All of lore.kernel.org
 help / color / mirror / Atom feed
From: Maxime Ripard <maxime.ripard@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] ltrace hangings
Date: Wed, 29 Feb 2012 14:03:48 +0100	[thread overview]
Message-ID: <4F4E2234.7030301@free-electrons.com> (raw)
In-Reply-To: <201202282333.58717.yann.morin.1998@free.fr>

Hi Yann,

On 28/02/2012 23:33, Yann E. MORIN wrote:
> On Tuesday 28 February 2012 17:47:40 Maxime Ripard wrote:
>> 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 ?
> 
> 0.5.3 is now a bit old (2 years), and there has been a new release
> about four months ago:
>   http://anonscm.debian.org/gitweb/?p=collab-maint/ltrace.git;a=summary
> 
> Maybe it's time we upgrade crosstool-NG to this new version...

I've upgraded the package in buildroot to 0.6.0, and same problem here
on ARM. However, it works fine on x86 either using directly their
build-system and Ubuntu's gcc or using buildroot's internal toolchain
for x86 (with uClibc).

It seems like the bug is probably more arch-specific than I thought.


-- 
Maxime Ripard, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com

      reply	other threads:[~2012-02-29 13:03 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-28 16:47 [Buildroot] ltrace hangings Maxime Ripard
2012-02-28 22:33 ` Yann E. MORIN
2012-02-29 13:03   ` Maxime Ripard [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=4F4E2234.7030301@free-electrons.com \
    --to=maxime.ripard@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 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.