From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 8066] nodejs crashes when built with gcc 4.9
Date: Wed, 02 Dec 2015 22:58:42 +0000 [thread overview]
Message-ID: <bug-8066-163-G7pcntx3vV@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-8066-163@https.bugs.busybox.net/>
https://bugs.busybox.net/show_bug.cgi?id=8066
--- Comment #8 from Martin <martin@barkynet.com> ---
(In reply to Jeroen Roovers from comment #6)
> On an ARM system (cortex-a7) I am seeing a similar problem when I build
> everything with gcc-4.9.*. It doesn't crash, though, it merely exits certain
> functions early, causing it to output invalid HTTP headers. I have seen some
> references on the wider Internet pointing to similar problems, but those
> were not connected to a specific GCC version or even the same OS. The only
> thing I am certain of is that GCC 4.9 miscompiles nodejs, including version
> 4.1.1. I haven't tried with libuv and libhttpparser properly in place,
> though.
I think this might be a different issue, the original issue is about a crash.
If you think you still have an issue can you please raise a new bug. In the
bug please attach a minimal non-working Buildroot configuration so we can try
to reproduce it.
Thanks
Martin
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2015-12-02 22:58 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-30 11:05 [Buildroot] [Bug 8066] New: nodejs crashes when built with gcc 4.9 bugzilla at busybox.net
2015-06-03 15:19 ` [Buildroot] [Bug 8066] " bugzilla at busybox.net
2015-06-10 8:53 ` bugzilla at busybox.net
2015-06-10 8:54 ` bugzilla at busybox.net
2015-06-10 8:55 ` bugzilla at busybox.net
2015-06-10 9:00 ` bugzilla at busybox.net
2015-09-30 12:55 ` bugzilla at busybox.net
2015-12-02 19:38 ` bugzilla at busybox.net
2015-12-02 22:49 ` bugzilla at busybox.net
2015-12-02 22:58 ` bugzilla at busybox.net [this message]
2015-12-03 11:37 ` bugzilla at busybox.net
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=bug-8066-163-G7pcntx3vV@https.bugs.busybox.net/ \
--to=bugzilla@busybox.net \
--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.