On Mon, Nov 22, 2010 at 02:34:29PM +0100, Roger Jeurninck wrote:
> the version which we use is 2.17.
That's over 4 years old! We are about to release 2.21. I recall
fixing one uninitialised memory bug in that time. There were likely
others too.
--
Alan Modra
Australia Development Lab, IBM
__
http://sourceware.org/bugzilla/show_bug.cgi?id=4907
Rainer Orth changed:
What|Removed |Added
CC||ro at TechFak dot
|
http://sourceware.org/bugzilla/show_bug.cgi?id=12253
--- Comment #1 from Rainer Orth 2010-11-22
17:52:07 UTC ---
Created attachment 5134
--> http://sourceware.org/bugzilla/attachment.cgi?id=5134
testcase
--
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
--- You
http://sourceware.org/bugzilla/show_bug.cgi?id=12253
Summary: .eh_frame_hdr not properly sorted with mixed .eh_frame
encodings
Product: binutils
Version: unspecified
Status: NEW
Severity: normal
Priority: P2
http://sourceware.org/bugzilla/show_bug.cgi?id=12240
--- Comment #1 from H.J. Lu 2010-11-22 16:58:35
UTC ---
None of the following operators can be used as label:
{ "and", O_bit_and, 2 },
{ "eq", O_eq, 2 },
{ "ge", O_ge, 2 },
{ "gt", O_gt, 2 },
{ "le", O_le, 2 },
{ "lt",
Hi Alan,
the version which we use is 2.17.
greetings,
Roger
2010/11/22 Alan Modra
> On Mon, Nov 22, 2010 at 01:54:58PM +0100, Roger Jeurninck wrote:
> > I'm running into build behaviour which might be caused by a
> > non-deterministic GNU linker?!
>
> This could be caused by ld reading uninit
On Mon, Nov 22, 2010 at 01:54:58PM +0100, Roger Jeurninck wrote:
> I'm running into build behaviour which might be caused by a
> non-deterministic GNU linker?!
This could be caused by ld reading uninitialised memory. A tool like
valgrind is useful in tracking down such things. What version of GN
Hi,
I'm running into build behaviour which might be caused by a
non-deterministic GNU linker?! As this is quiet unlikely I hope you can
support me in reducing this issue so I can find the real root cause.
Thanks,
Roger
--
What is the issue?
at the c
