libiberty vasprintf bug, doesn't handle long longs

Who owns libiberty? Do I file a bugzilla for binutils or gcc or ? vasprintf doesn't watch for long longs so the va_arg() calls can get out of sync with what's passed. diff -u -p -r1.2 vasprintf.c --- vasprintf.c 19 Oct 2005 01:28:44 - 1.2 +++ vasprintf.c 10 Jan 2006 17:02:27 - @@ -1

Re: libiberty vasprintf bug, doesn't handle long longs

Doug Evans <[EMAIL PROTECTED]> writes: > Who owns libiberty? Do I file a bugzilla for binutils or gcc or ? gcc owns libiberty, so: http://gcc.gnu.org/bugzilla/ > vasprintf doesn't watch for long longs so the va_arg() calls > can get out of sync with what's passed. Yeah, vasprintf probably need

Re: Odd crash with strip

On Wed, Jan 11, 2006 at 08:43:53AM +1030, Alan Modra wrote: > * objcopy.c (copy_object): Set isympp and osympp to NULL after free. Reviewing my own patch before committing would have been better.. There was a good reason why the test is "osympp != isympp" rather than "osympp != NULL", and ch

Re: Odd crash with strip

On Tue, Jan 10, 2006 at 01:42:34AM -0600, R.K. wrote: > # strip bash checkpassword cp > BFD: checkpassword: warning: Empty loadable segment detected, is this > intentional ? > > BFD: checkpassword: warning: Empty loadable segment detected, is this > intentional ? > > strip: there are no section