https://sourceware.org/bugzilla/show_bug.cgi?id=24803
--- Comment #1 from Tom Tromey ---
In bug #24820, I'm rewriting the gdb .debug_names reader and writer
to be closer to what is specified by DWARF. A few extensions are
needed, so if this is ever implemented in gold, it should emit those
as we
https://sourceware.org/bugzilla/show_bug.cgi?id=31133
Bug ID: 31133
Summary: [riscv64] -z now breaks glibc testsuite
Product: binutils
Version: 2.41
Status: NEW
Severity: normal
Priority: P2
Component: ld
https://sourceware.org/bugzilla/show_bug.cgi?id=31133
Aurelien Jarno changed:
What|Removed |Added
Host||riscv64-unknown-linux-gnu
https://sourceware.org/bugzilla/show_bug.cgi?id=31133
--- Comment #1 from Aurelien Jarno ---
Created attachment 15251
--> https://sourceware.org/bugzilla/attachment.cgi?id=15251&action=edit
Reproducer
I have attached a (big) reproduced for this bug. This is basically the files
from the glibc b
https://sourceware.org/bugzilla/show_bug.cgi?id=31130
Alan Modra changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://sourceware.org/bugzilla/show_bug.cgi?id=31131
Alan Modra changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://sourceware.org/bugzilla/show_bug.cgi?id=31134
Bug ID: 31134
Summary: 2.41: build fails with --enable-warn-execstack
Product: binutils
Version: 2.41
Status: UNCONFIRMED
Severity: normal
Priority: P2
Compon
https://sourceware.org/bugzilla/show_bug.cgi?id=31134
--- Comment #1 from kloczek ---
Looks like DEFAULT_LD_ERROR_EXECSTACK is defined only when
--disable-error-rwx-segments is used.
[tkloczko@pers-jacek ld]$ grep -r DEFAULT_LD_ERROR_EXECSTACK
emultempl/elf.em: link_info.error_execstack = DEFAU
https://sourceware.org/bugzilla/show_bug.cgi?id=31134
kloczek changed:
What|Removed |Added
Summary|2.41: build fails with |2.41: build fails with
|-
https://sourceware.org/bugzilla/show_bug.cgi?id=31134
--- Comment #2 from kloczek ---
Correction when --enaable-warn-execstack
--
You are receiving this mail because:
You are on the CC list for the bug.
Package: libbinutils
Version: 2.41.50.20231206-1
Valgrind reports a leak when using bfd_find_nearest_line():
==2681185== 145,802 bytes in 1 blocks are definitely lost in loss record 39
of 39
==2681185==at 0x4840808: malloc (in
/usr/libexec/valgrind/vgpreload_memcheck-amd64-linux.so)
==2681185
https://sourceware.org/bugzilla/show_bug.cgi?id=31131
--- Comment #2 from yuxuan He <1157401338 at qq dot com> ---
(In reply to Alan Modra from comment #1)
> Already fixed. 2.32 is old. You should look at current source if you want
> to help improve binutils. git clone
> https://sourceware.org/
https://sourceware.org/bugzilla/show_bug.cgi?id=31131
--- Comment #3 from yuxuan He <1157401338 at qq dot com> ---
thanks for your reply. 2.32 is old but i've check this bug still existing in
current version. and there are several system still use 2.32 as there default
version.for example, ubuntu
https://sourceware.org/bugzilla/show_bug.cgi?id=31130
--- Comment #2 from yuxuan He <1157401338 at qq dot com> ---
actually, i don't mean that XNEWVEC return a stack address, i mean "depth" is
stack address and it has been store into new_storage
--
You are receiving this mail because:
You are on
https://sourceware.org/bugzilla/show_bug.cgi?id=31130
--- Comment #3 from Alan Modra ---
(In reply to yuxuan He from comment #2)
> actually, i don't mean that XNEWVEC return a stack address, i mean "depth"
> is stack address and it has been store into new_storage
That too is not a problem. Given
https://sourceware.org/bugzilla/show_bug.cgi?id=31130
--- Comment #4 from yuxuan He <1157401338 at qq dot com> ---
ok thanks
--
You are receiving this mail because:
You are on the CC list for the bug.
On Sun, Dec 10, 2023 at 09:45:32PM -0300, Konstantin Isakov wrote:
> --- a/bfd/dwarf2.c 2023-11-25 04:59:00.0 -0300
> +++ b/bfd/dwarf2.c 2023-12-10 21:05:02.084673848 -0300
> @@ -6123,6 +6123,7 @@
>free (file->dwarf_line_str_buffer);
>free (file->dwarf_str_buffer);
>
17 matches
Mail list logo
