Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Luis Machado <luisgpm@linux.vnet.ibm.com>
To: Jim Blandy <jimb@codesourcery.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH] solib-svr4.c, several memory leaks
Date: Thu, 09 Aug 2007 22:45:00 -0000	[thread overview]
Message-ID: <1186699535.4524.14.camel@localhost> (raw)
In-Reply-To: <21109.12.7.175.2.1186596556.squirrel@webmail.sonic.net>

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.

Backtrace output:
-------
Program received signal SIGSEGV, Segmentation fault.
0x00000400002a8b30 in .strcmp () from /lib64/tls/libc.so.6
(gdb) bt
#0  0x00000400002a8b30 in .strcmp () from /lib64/tls/libc.so.6
#1  0x0000000010089d14 in bfd_lookup_symbol (abfd=0x1095a980,
symname=0x106de700 "r_debug_state")
    at gdb-head/gdb/solib-svr4.c:305
-------

Best regards,
Luis

On Wed, 2007-08-08 at 11:09 -0700, msnyder@sonic.net wrote:
> >
> > msnyder@sonic.net writes:
> >> 2007-08-04  Michael Snyder  <msnyder@access-company.com>
> >>
> >> 	* solib-svr4.c (open_symbol_file_object): Memory leak.
> >> 	(svr4_current_sos): Ditto.
> >> 	(enable_break): Ditto.
> >
> > Looks okay to me.
> 
> Committed.  Thanks Jim and Kevin.
> 
> 
-- 
Luis Machado
Software Engineer 
IBM Linux Technology Center
LoP Toolchain/Debuggers' team
Phone: +55 19-2132-2218
T/L: 839-2218
e-mail: luisgpm@vnet.linux.ibm.com


  reply	other threads:[~2007-08-09 22:45 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 [this message]
     [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

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=1186699535.4524.14.camel@localhost \
    --to=luisgpm@linux.vnet.ibm.com \
    --cc=gdb-patches@sourceware.org \
    --cc=jimb@codesourcery.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