Re: Issue 387378117: binutils:fuzz_dlltool: Direct-leak in xmalloc

2025-02-20 Thread buganizer-system

Replying to this email means your email address will be shared with the
team that works on this product.
https://issues.oss-fuzz.com/issues/387378117

Changed
access level:  Limited visibility → Default access

pe...@google.com added comment #3:

This bug has been fixed. It has been opened to the public.

___

Reference Info: 387378117 binutils:fuzz_dlltool: Direct-leak in xmalloc
component:  Public Trackers > 1362134 > OSS Fuzz
status:  Verified
reporter:  87...@developer.gserviceaccount.com
assignee:  cl...@appspot.gserviceaccount.com
verifier:  cl...@appspot.gserviceaccount.com
cc:  am...@gmail.com, bug-binutils@gnu.org, da...@adalogics.com, and 2 more
collaborators:  co...@oss-fuzz.com
type:  Bug
access level:  Default access
priority:  P2
severity:  S4
hotlist:  ClusterFuzz-Verified, Reproducible, Stability-LibFuzzer,
Stability-Memory-AddressSanitizer, Stability-Memory-LeakSanitizer
retention:  Component default
Disclosure:  Apr 4, 2025
Project:  binutils
Reported:  Jan 4, 2025


Generated by Google IssueTracker notification system.

You're receiving this email because you are subscribed to updates on Google
IssueTracker issue 387378117
Unsubscribe from this issue.


[Bug ld/32720] ld: add --why-live

2025-02-20 Thread pinskia at gcc dot gnu.org
https://sourceware.org/bugzilla/show_bug.cgi?id=32720

Andrew Pinski  changed:

   What|Removed |Added

 CC||pinskia at gcc dot gnu.org

--- Comment #1 from Andrew Pinski  ---
Seems badly named option.

why_referenced seems like a better name.

-- 
You are receiving this mail because:
You are on the CC list for the bug.


Re: Issue 387378117: binutils:fuzz_dlltool: Direct-leak in xmalloc

2025-02-20 Thread buganizer-system

Replying to this email means your email address will be shared with the
team that works on this product.
https://issues.oss-fuzz.com/issues/387378117

Changed
status:  New → Verified
assignee:   → cl...@appspot.gserviceaccount.com
verifier:   → cl...@appspot.gserviceaccount.com

87...@developer.gserviceaccount.com added comment #2:
ClusterFuzz testcase 5498030657503232 is verified as fixed in
https://oss-fuzz.com/revisions?job=afl_asan_binutils&range=202502190646:202502200634

If this is incorrect, please file a bug on
https://github.com/google/oss-fuzz/issues/new
___

Reference Info: 387378117 binutils:fuzz_dlltool: Direct-leak in xmalloc
component:  Public Trackers > 1362134 > OSS Fuzz
status:  Verified
reporter:  87...@developer.gserviceaccount.com
assignee:  cl...@appspot.gserviceaccount.com
verifier:  cl...@appspot.gserviceaccount.com
cc:  am...@gmail.com, bug-binutils@gnu.org, da...@adalogics.com, and 2 more
collaborators:  co...@oss-fuzz.com
type:  Bug
access level:  Limited visibility
priority:  P2
severity:  S4
hotlist:  Reproducible, Stability-LibFuzzer,
Stability-Memory-AddressSanitizer, Stability-Memory-LeakSanitizer
retention:  Component default
Disclosure:  Apr 4, 2025
Project:  binutils
Reported:  Jan 4, 2025


Generated by Google IssueTracker notification system.

You're receiving this email because you are subscribed to updates on Google
IssueTracker issue 387378117
Unsubscribe from this issue.