From: Markus Deuling <deuling@de.ibm.com>
To: msnyder@sonic.net
Cc: luisgpm@linux.vnet.ibm.com, gdb-patches@sourceware.org,
jimb@codesourcery.com, kevinb@redhat.com
Subject: Re: [PATCH] solib-svr4.c, several memory leaks
Date: Fri, 10 Aug 2007 07:16:00 -0000 [thread overview]
Message-ID: <46BC1052.1090303@de.ibm.com> (raw)
In-Reply-To: <21641.12.7.175.2.1186704765.squirrel@webmail.sonic.net>
msnyder@sonic.net schrieb:
> Jim, Kevin,
>
> Apparently we can't free the tmp name while bfd has the file open.
> Moving the xfree to later, after it has been closed, seems to fix
> the segfault.
>
> See attached patch.
> Michael
>
>> Folks,
>>
>> GDB started acting strange today, segfaulting when trying to open some
>> binaries, GDB itself included. Other binaries would work OK.
>>
>> Log:
>>
>> -------
>> ~/builds/gdb-head/> gdb-head-64bit/gdb/gdb gdb-head-64bit/gdb/gdb
>> GNU gdb 6.6.50.20070809-cvs
>> Copyright (C) 2007 Free Software Foundation, Inc.
>> GDB is free software, covered by the GNU General Public License, and you
>> are
>> welcome to change it and/or distribute copies of it under certain
>> conditions.
>> Type "show copying" to see the conditions.
>> There is absolutely no warranty for GDB. Type "show warranty" for
>> details.
>> This GDB was configured as "powerpc64-unknown-linux-gnu"...
>> startUsing host libthread_db library "/lib64/ppc970/libthread_db.so.1".
>> (gdb) start
>> Breakpoint 1 at 0x10060b3c: file gdb-head/gdb/gdb.c, line 30.
>> Starting program: gdb-head-64bit/gdb/gdb
>> BFD: reopening : No such file or directory
>>
>> Segmentation fault
>> -------
>>
>>
>> I tracked down the root of the problem and this patch appears to be the
>> problem. Reverting it back fixes the problem.
>
Yes, it does. Please commit. These are my current testsuite results on x86 :-( :
# of expected passes 5706
# of unexpected failures 1233
<...>
# of unresolved testcases 4334
--
Markus Deuling
GNU Toolchain for Linux on Cell BE
deuling@de.ibm.com
prev parent reply other threads:[~2007-08-10 7:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-05 3:02 msnyder
2007-08-06 22:14 ` Jim Blandy
2007-08-06 22:43 ` Kevin Buettner
2007-08-08 18:09 ` msnyder
2007-08-09 22:45 ` Luis Machado
[not found] ` <1186699391.4524.12.camel@localhost>
2007-08-09 23:39 ` msnyder
2007-08-10 0:13 ` msnyder
2007-08-10 7:16 ` Markus Deuling [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=46BC1052.1090303@de.ibm.com \
--to=deuling@de.ibm.com \
--cc=gdb-patches@sourceware.org \
--cc=jimb@codesourcery.com \
--cc=kevinb@redhat.com \
--cc=luisgpm@linux.vnet.ibm.com \
--cc=msnyder@sonic.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox