https://sourceware.org/bugzilla/show_bug.cgi?id=31120
Bug ID: 31120
Summary: ld-scripts/fill2 fails when bfd_vma is 32 bits
Product: binutils
Version: 2.42 (HEAD)
Status: NEW
Severity: normal
Priority: P2
Compone
https://sourceware.org/bugzilla/show_bug.cgi?id=31116
Vladimir Mezentsev changed:
What|Removed |Added
Status|NEW |ASSIGNED
--
You are receiving t
Updates:
Labels: -restrict-view-commit
Comment #3 on issue 63742 by sheriffbot: binutils:fuzz_objdump_safe: Segv on
unknown address in bfd_getl32
https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=63742#c3
This bug has been fixed. It has been opened to the public.
- Your friendly She
Updates:
Labels: -restrict-view-commit
Comment #3 on issue 63660 by sheriffbot: binutils:fuzz_objdump: Direct-leak in
xmalloc
https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=63660#c3
This bug has been fixed. It has been opened to the public.
- Your friendly Sheriffbot
--
You rec
https://sourceware.org/bugzilla/show_bug.cgi?id=31109
--- Comment #7 from Vladimir Mezentsev
---
I configured my gcc trank build:
/configure --prefix=`pwd`/INSTALL --enable-gprofng
I see the binutils-gdb targets in Makefile.
For example:
% grep gprof Makefile
maybe-configure-gprof \
https://sourceware.org/bugzilla/show_bug.cgi?id=31115
--- Comment #2 from Thiago Jung Bauermann
---
(In reply to Nick Clifton from comment #1)
> Created attachment 15240 [details]
> Proposed patch
>
> Hi Thiago,
>
> Please could you try out this patch and let me know if it works for you ?
>
https://sourceware.org/bugzilla/show_bug.cgi?id=31115
--- Comment #1 from Nick Clifton ---
Created attachment 15240
--> https://sourceware.org/bugzilla/attachment.cgi?id=15240&action=edit
Proposed patch
Hi Thiago,
Please could you try out this patch and let me know if it works for you ?
Ch
https://sourceware.org/bugzilla/show_bug.cgi?id=31115
Nick Clifton changed:
What|Removed |Added
Assignee|unassigned at sourceware dot org |nickc at redhat dot com
Eve
;action=edit
test log
this fails with trunk 20231206, attaching the test log. There seems to be
something wrong with the shell script. In the /gprofng I see an
unexpected file:
ls builddir-single/gprofng/
'&1'config.logdoc gprofng.sumMa