[Bug binutils/2015] Segfault in setlocale() call makes programs unusable

2007-08-06 Thread amodra at bigpond dot net dot au
--- Additional Comments From amodra at bigpond dot net dot au 2007-08-07 06:23 --- Fix available, and not a binutils bug. -- What|Removed |Added Status|WAITING

[Bug ld/2112] Binutils LD fails at line 6419 of elflink.c

2007-08-06 Thread amodra at bigpond dot net dot au
--- Additional Comments From amodra at bigpond dot net dot au 2007-08-07 06:18 --- I'm reasonably confident this has been fixed, and this bug has been in "waiting" for a long time. -- What|Removed |Added ---

[Bug ld/4538] add --all-init flag to force all static initializers to be loaded

2007-08-06 Thread ian at airs dot com
--- Additional Comments From ian at airs dot com 2007-08-07 05:30 --- What advantage will --all-init bring you over --whole-archive? How would you define --all-init in terms of the linker? You are defining it in terms of C++. But different C++ implementations handle static constructors

[Bug ld/4538] add --all-init flag to force all static initializers to be loaded

2007-08-06 Thread cnmnzusoib at mailinator dot com
--- Additional Comments From cnmnzusoib at mailinator dot com 2007-08-07 05:17 --- Apparently not. :-P Now, disabling my bugzilla account -- that's *really* classy. Glad to know I'm dealing with a professional adult, not a hyperventilating dictator-for-life ("because I said so, that

[Bug ld/4538] add --all-init flag to force all static initializers to be loaded

2007-08-06 Thread amodra at bigpond dot net dot au
--- Additional Comments From amodra at bigpond dot net dot au 2007-08-07 04:25 --- This isn't a debating society. -- What|Removed |Added Status|REOPENED

[Bug ld/4538] add --all-init flag to force all static initializers to be loaded

2007-08-06 Thread ejt at andrew dot cmu dot edu
--- Additional Comments From ejt at andrew dot cmu dot edu 2007-08-07 03:37 --- Such a good, persuasive argument! You've raised many good points that I hadn't considered... OK then, lets call it an "enhancement", and I'll reword the summary for you. The fact that this issue keeps comi

[Bug gas/4414] unrecognized option `-mc68020'

2007-08-06 Thread amodra at bigpond dot net dot au
--- Additional Comments From amodra at bigpond dot net dot au 2007-08-07 01:32 --- m68k-coff is no longer supported. You'll need to use an older binutils. -- What|Removed |Added

[Bug ld/4515] bad definition of start address in ldscripts for OMAGIC

2007-08-06 Thread amodra at bigpond dot net dot au
--- Additional Comments From amodra at bigpond dot net dot au 2007-08-07 01:27 --- As Nick says, current x86-aout scripts have . = 0. -- What|Removed |Added Stat

[Bug ld/4538] static initialization ignored in static archive (.a)

2007-08-06 Thread amodra at bigpond dot net dot au
--- Additional Comments From amodra at bigpond dot net dot au 2007-08-07 01:22 --- Not a bug. Please do not reopen. -- What|Removed |Added Status|REOPENED

[Bug libc/4781] binutils 2.17.50.0.7 and later eats up memory when calling gnujava wizards in OpenOffice

2007-08-06 Thread drow at sources dot redhat dot com
--- Additional Comments From drow at sources dot redhat dot com 2007-08-06 19:38 --- Oh, I see. Without that unwinder patch, if the PC wasn't saved we'll end up with a segfault. Since this is coming through Java, I assume we're getting the unwinder re-invoked from the signal handler, a

[Bug libc/4781] binutils 2.17.50.0.7 and later eats up memory when calling gnujava wizards in OpenOffice

2007-08-06 Thread jakub at redhat dot com
--- Additional Comments From jakub at redhat dot com 2007-08-06 18:59 --- I have posted an unwinder patch in the thread I referenced, see http://gcc.gnu.org/ml/gcc/2006-12/msg00312.html but that was without ChangeLog entry, I got no feedback and forgot about it (because in the meantime I

[Bug libc/4781] binutils 2.17.50.0.7 and later eats up memory when calling gnujava wizards in OpenOffice

2007-08-06 Thread drow at sources dot redhat dot com
--- Additional Comments From drow at sources dot redhat dot com 2007-08-06 18:52 --- HJ suggested this bug should be resolved before 2.18, but that was the day before the glibc patch was identified. Could someone explain to me, in small words, how Jakub's patch could "cause" this if it

[Bug binutils/4791] Update to latest gnustandards (Was: etc/standards.texi: @strong{Note...} produces a spurious cross-reference in Info)

2007-08-06 Thread nightstrike at gmail dot com
--- Additional Comments From nightstrike at gmail dot com 2007-08-06 17:38 --- I changed the title to reflect that. What else must be done to upgrade to the latest version? -- What|Removed |Added --

Re: [incomplete patch] Get objdump to report exception tables for ARM/SH4 correctly

2007-08-06 Thread Nick Clifton
Hi Danny, 2. Cleanup in my_symbol_for_address. There's none now. Should there be? Yes. :-) Also it looks like my_symbol_for_address is going to quite slow for large symbol tables. You might want to consider ensuring that the symbol time is sorted by address and then performing some kind o

[Bug binutils/4791] etc/standards.texi: @strong{Note...} produces a spurious cross-reference in Info

2007-08-06 Thread nickc at redhat dot com
--- Additional Comments From nickc at redhat dot com 2007-08-06 14:26 --- Subject: Re: etc/standards.texi: @strong{Note...} produces a spurious cross-reference in Info Hi, > I have reviewed the current version of the standards.texi file. Should this > bug > report be the one t

Re: [Bug binutils/4791] etc/standards.texi: @strong{Note...} produces a spurious cross-reference in Info

2007-08-06 Thread Nick Clifton
Hi, I have reviewed the current version of the standards.texi file. Should this bug report be the one that requests updating to the latest version of "gnustandards", or is that in the project plan for binutils somewhere? This bug report is fine. Cheers Nick __

[incomplete patch] Get objdump to report exception tables for ARM/SH4 correctly

2007-08-06 Thread Danny Backx
[Retry to send this message without the attachment that probably blocked the earlier attempt.] I've attached a patch that'll get objdump to report exception tables correctly for ARM and SH4 which, according to MSDN, have a different format for storing the pdata segment. Here's part of the output