From: ing. Federico Fuga <fuga@studiofuga.com>
To: buildroot@busybox.net
Subject: [Buildroot] Illegal Instruction in arm buildroot
Date: Thu, 15 Nov 2007 15:43:52 +0100 [thread overview]
Message-ID: <473C5B28.7090906@studiofuga.com> (raw)
In-Reply-To: <203109.65849.qm@web26215.mail.ukl.yahoo.com>
Hi again,
I was meaning that I cannot find the SOFT_FLOAT options for the
buildroot toolchain building, maybe I had to search in the scripts (.mk).
But I have found the problem for the busybox (wget et al.), by
disableing the MONOTONIC_SYSCALL option now busybox works correctly
(wget and udhcpc doesn't crash anymore).
The problem persist with udevd (144 and 116 versions), but I think I
have traced the problem to the inotify syscall:
Core was generated by `./udevd'.
Program terminated with signal 4, Illegal instruction.
#0 0x40016cc0 in syscall () from /lib/libc.so.0
(gdb) bt
#0 0x40016cc0 in syscall () from /lib/libc.so.0
#1 0x0000a9b4 in main (argc=<value optimized out>,
argv=<value optimized out>, envp=<value optimized out>)
at udev_sysdeps.h:116
(gdb)
and (for udev v.116) line 116 is
static inline int inotify_init(void)
{
return syscall(__NR_inotify_init);
}
BTW, I have checked your suggestion and find that at boot:
NetWinder Floating Point Emulator V0.97 (double
precision)
and a simple program that performs and prints 4.0/1.33 is compiled and
executed correctly (so FP unit is working, it seems.)
Thank you again for your suggestions.
Regards,
ing. Federico Fuga
next prev parent reply other threads:[~2007-11-15 14:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-15 14:09 [Buildroot] Illegal Instruction in arm buildroot Michael Trimarchi
2007-11-15 14:43 ` ing. Federico Fuga [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-11-15 13:39 Michael Trimarchi
2007-11-15 13:58 ` ing. Federico Fuga
2007-11-15 13:17 ing. Federico Fuga
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=473C5B28.7090906@studiofuga.com \
--to=fuga@studiofuga.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