[Bug binutils/29915] bfdio.c does not compile with mingw.org's MinGW

2022-12-18 Thread amodra at gmail dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=29915

--- Comment #1 from Alan Modra  ---
Can we have a bfd/configure.ac AC_CHECK_DECL test instead?

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


[Bug binutils/29915] bfdio.c does not compile with mingw.org's MinGW

2022-12-18 Thread eliz at gnu dot org
https://sourceware.org/bugzilla/show_bug.cgi?id=29915

--- Comment #2 from Eli Zaretskii  ---
(In reply to Alan Modra from comment #1)
> Can we have a bfd/configure.ac AC_CHECK_DECL test instead?

That would definitely work, but then someone else will have to write and test
the patch, sorry.

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


[Bug binutils/29915] bfdio.c does not compile with mingw.org's MinGW

2022-12-18 Thread eliz at gnu dot org
https://sourceware.org/bugzilla/show_bug.cgi?id=29915

--- Comment #3 from Eli Zaretskii  ---
(In reply to Eli Zaretskii from comment #2)
> (In reply to Alan Modra from comment #1)
> > Can we have a bfd/configure.ac AC_CHECK_DECL test instead?
> 
> That would definitely work, but then someone else will have to write and
> test the patch, sorry.

Btw, even with AC_CHECK_DECL test, the result will need to be conditioned by
something like "#ifdef _WIN32", since Posix hosts don't have this function, but
we probably don't want them to compile a prototype which uses Win32-isms like
_CRTIMP, right?

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


Issue 54323 in oss-fuzz: binutils:fuzz_addr2line: Out-of-memory in fuzz_addr2line

2022-12-18 Thread sheriffbot via monorail
Updates:
Labels: -restrict-view-commit

Comment #3 on issue 54323 by sheriffbot: binutils:fuzz_addr2line: Out-of-memory 
in fuzz_addr2line
https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=54323#c3

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

- Your friendly Sheriffbot

-- 
You received this message because:
  1. You were specifically CC'd on the issue

You may adjust your notification preferences at:
https://bugs.chromium.org/hosting/settings

Reply to this email to add a comment.