From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] Strange hang while executing commands
Date: Thu, 17 Feb 2011 21:47:15 +0100 [thread overview]
Message-ID: <87sjvm75ik.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <AANLkTikvXk7qzFov-25Xu_MmUXdkYMdwkKkGtsRzhUwA@mail.gmail.com> (Martin Hicks's message of "Mon, 14 Feb 2011 14:18:17 -0500")
>>>>> "Martin" == Martin Hicks <mort@bork.org> writes:
Martin> Hi,
Martin> Does anyone have any clues where I might start looking for the reason
Martin> behind commands within the procps package just hanging?
Hanging or crashing?
Martin> mprotect(0xffa9000, 16384, PROT_READ) = 0 <0.000104>
Martin> mprotect(0x4802e000, 4096, PROT_READ) = 0 <0.000077>
Martin> munmap(0x4801f000, 64) = 0 <0.000098>
Martin> uname({sys="Linux", node="targa4v2", ...}) = 0 <0.000115>
Martin> --- SIGINT (Interrupt) @ 0 (0) ---
Martin> +++ killed by SIGINT +++
This looks like a crash (a null pointer access). On what arch / with
what configuration is this?
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2011-02-17 20:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-14 19:18 [Buildroot] Strange hang while executing commands Martin Hicks
2011-02-17 20:47 ` Peter Korsgaard [this message]
2011-02-17 20:49 ` Martin Hicks
2011-03-28 20:08 ` Martin Hicks
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=87sjvm75ik.fsf@macbook.be.48ers.dk \
--to=jacmet@uclibc.org \
--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