https://sourceware.org/bugzilla/show_bug.cgi?id=17541
Bug ID: 17541
Summary: addr2line: function names in anonymous namespaces are
incorrectly reported.
Product: binutils
Version: 2.25
Status: NEW
Severity: norm
> .init_array is used by newer versions of gcc to serve the same purpose as
> .ctors,
> but using a different mechanism to run constructor code. Similarly for
> .fini_array.
> At a guess, your code is making assumptions about the order in which
> destructors
> are run. If you google for "g++ s
On Mon, Nov 03, 2014 at 08:34:20PM +, Douglas Graham wrote:
> Am I confused about what's actually in the .init_array and
> .fini_array sections? There is also .ctors and .dtors
> which I thought contains the static ctors and dtors.
.init_array is used by newer versions of gcc to serve the sam
https://sourceware.org/bugzilla/show_bug.cgi?id=17532
--- Comment #5 from Alan Modra ---
No, I don't think the old behaviour was particularly useful. If you want the
current directory to be searched, use -L.
git commit d4ae5fb0
https://sourceware.org/ml/binutils/2014-02/msg00097.html
The patch
https://sourceware.org/bugzilla/show_bug.cgi?id=17540
Bug ID: 17540
Summary: gold leaks processing an empty file
Product: binutils
Version: unspecified
Status: NEW
Severity: normal
Priority: P2
Component: gold
https://sourceware.org/bugzilla/show_bug.cgi?id=17512
--- Comment #54 from Alexander Cherepanov ---
Created attachment 7886
--> https://sourceware.org/bugzilla/attachment.cgi?id=7886&action=edit
More crashers for `objdump -x`
list.txt inside the archive lists various errors from valgrind (with
Thanks. That got me pointed in the right direction.
The problem does appear to be in the linker script, and I'm fairly sure that it
is related to the initialization order of
static constructors and/or destructors.
The 2.22 linker script does this:
.init_array :
{
KEEP (*(SORT_BY_IN
https://sourceware.org/bugzilla/show_bug.cgi?id=17538
Bug ID: 17538
Summary: --threads options cause random crashes with gcc 4.9.2
Product: binutils
Version: 2.24
Status: NEW
Severity: critical
Priority: P2
Compo
https://sourceware.org/bugzilla/show_bug.cgi?id=17512
--- Comment #53 from Alexander Cherepanov ---
Created attachment 7885
--> https://sourceware.org/bugzilla/attachment.cgi?id=7885&action=edit
valgrind output for 140849-0.004.exe
Shows a bunch of error of the following types:
- Use of uninit
https://sourceware.org/bugzilla/show_bug.cgi?id=17512
--- Comment #52 from Hanno Boeck ---
Nick, have you seen bug #17533 ? (ar archive crasher) That's still unfixed, all
others seem fine now.
I'll do a re-run on my large fuzzing samples collection.
--
You are receiving this mail because:
You a
https://sourceware.org/bugzilla/show_bug.cgi?id=17512
--- Comment #51 from Nick Clifton ---
Hi Hanno, Hi Alexander,
Please try the latest master binutils sources. They should be able to handle
the new test files gracefully.
Cheers
Nick
--
You are receiving this mail because:
You are on t
https://sourceware.org/bugzilla/show_bug.cgi?id=17533
Hanno Boeck changed:
What|Removed |Added
CC||hanno at hboeck dot de
--
You are rece
https://sourceware.org/bugzilla/show_bug.cgi?id=17512
--- Comment #50 from cvs-commit at gcc dot gnu.org ---
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "gdb and binutils".
The branch
https://sourceware.org/bugzilla/show_bug.cgi?id=17532
--- Comment #4 from maillist-gdb at barfooze dot de ---
oh. i see. thanks for the expanation.
however i'm curious if you agree that the old behaviour was more useful, even
though it was unintended ?
also i spent about 1 hour trying to find th
Hi Doug,
I'm not actually sure that this is a linker bug, but it sure looks
like one. Version 2.21.1a of ld works fine, but starting at version
2.22 and up to 2.24, we are seeing some odd behaviour that is hard to
pin down.
If you have a look at the ld/NEWS file in the sources you can see wha
15 matches
Mail list logo
