From: msnyder@sonic.net
To: luisgpm@linux.vnet.ibm.com, gdb-patches@sourceware.org
Cc: jimb@codesourcery.com, kevinb@redhat.com
Subject: Re: [PATCH] solib-svr4.c, several memory leaks
Date: Fri, 10 Aug 2007 00:13:00 -0000 [thread overview]
Message-ID: <21641.12.7.175.2.1186704765.squirrel@webmail.sonic.net> (raw)
In-Reply-To: <1186699391.4524.12.camel@localhost>
[-- Attachment #1: Type: text/plain, Size: 1258 bytes --]
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.
[-- Attachment #2: enable_break.txt --]
[-- Type: text/plain, Size: 1050 bytes --]
Index: solib-svr4.c
===================================================================
RCS file: /cvs/src/src/gdb/solib-svr4.c,v
retrieving revision 1.72
diff -p -r1.72 solib-svr4.c
*** solib-svr4.c 8 Aug 2007 18:08:52 -0000 1.72
--- solib-svr4.c 10 Aug 2007 00:09:19 -0000
*************** enable_break (void)
*** 1008,1014 ****
tmp_fd = solib_open (buf, &tmp_pathname);
if (tmp_fd >= 0)
tmp_bfd = bfd_fopen (tmp_pathname, gnutarget, FOPEN_RB, tmp_fd);
- xfree (tmp_pathname);
if (tmp_bfd == NULL)
goto bkpt_at_symbol;
--- 1008,1013 ----
*************** enable_break (void)
*** 1102,1107 ****
--- 1101,1107 ----
/* For whatever reason we couldn't set a breakpoint in the dynamic
linker. Warn and drop into the old code. */
bkpt_at_symbol:
+ xfree (tmp_pathname);
warning (_("Unable to find dynamic linker breakpoint function.\n"
"GDB will be unable to debug shared library initializers\n"
"and track explicitly loaded dynamic code."));
next prev parent reply other threads:[~2007-08-10 0:13 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 [this message]
2007-08-10 7:16 ` Markus Deuling
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=21641.12.7.175.2.1186704765.squirrel@webmail.sonic.net \
--to=msnyder@sonic.net \
--cc=gdb-patches@sourceware.org \
--cc=jimb@codesourcery.com \
--cc=kevinb@redhat.com \
--cc=luisgpm@linux.vnet.ibm.com \
/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