From: Michael Snyder <msnyder@specifix.com>
To: Daniel Jacobowitz <drow@false.org>
Cc: Paul Pluzhnikov <ppluzhnikov@google.com>,
gdb-patches@sourceware.org, Doug Evans <dje@google.com>
Subject: Re: [RFC] Fix for mishandling of "break 'pthread_create@GLIBC_2.2.5'"
Date: Tue, 13 May 2008 22:16:00 -0000 [thread overview]
Message-ID: <1210710229.4615.566.camel@localhost.localdomain> (raw)
In-Reply-To: <20080513184447.GA12349@caradoc.them.org>
On Tue, 2008-05-13 at 14:44 -0400, Daniel Jacobowitz wrote:
> On Tue, May 13, 2008 at 11:35:53AM -0700, Paul Pluzhnikov wrote:
> > 2008-05-13 Paul Pluzhnikov <ppluzhnikov@google.com>
> >
> > * linespec.c (locate_first_half): Rename to...
> > (locate_first_half_1): ... this.
> > (locate_first_half): New fn.
> >
>
> Patch missing?
>
> Rather than making versions special, can we suppress looking for
> fields inside quoted strings? GCC names static variables "foo.1" and
> it's hard to get GDB to display that.
FYI, there's a sort-of work-around...
(gdb) rb pthread_create
Function "pthread_create" not defined.
Make breakpoint pending on future shared library load? (y or [n]) n
<function, no debug info> pthread_create@plt;
Breakpoint 2 at 0xc746a6
<function, no debug info> __pthread_create_2_1;
Can't find member of namespace, class, struct, or union named
"pthread_create@@GLIBC_2.1"
Hint: try 'pthread_create@@GLIBC_2.1<TAB> or
'pthread_create@@GLIBC_2.1<ESC-?>
(Note leading single quote.)
<function, no debug info> pthread_create@@GLIBC_2.1;
Breakpoint 3 at 0xc75145
<function, no debug info> __pthread_create_2_0;
Can't find member of namespace, class, struct, or union named
"pthread_create@GLIBC_2.0"
Hint: try 'pthread_create@GLIBC_2.0<TAB> or
'pthread_create@GLIBC_2.0<ESC-?>
(Note leading single quote.)
<function, no debug info> pthread_create@GLIBC_2.0;
(gdb) i b
Num Type Disp Enb Address What
1 breakpoint keep y 0x0804846f in main at t.c:7
breakpoint already hit 1 time
2 breakpoint keep y 0x00c746a6 <pthread_create@@GLIBC_2.1+6>
3 breakpoint keep y 0x00c75145 <pthread_create@GLIBC_2.0+5>
next prev parent reply other threads:[~2008-05-13 20:24 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-13 19:11 Paul Pluzhnikov
2008-05-13 19:21 ` Daniel Jacobowitz
2008-05-13 22:16 ` Michael Snyder [this message]
2008-05-13 23:02 ` Paul Pluzhnikov
2008-05-13 23:16 ` Daniel Jacobowitz
2008-05-14 1:05 ` Paul Pluzhnikov
2008-05-14 8:16 ` Paul Pluzhnikov
2008-06-05 19:14 ` Daniel Jacobowitz
2008-06-06 2:14 ` Paul Pluzhnikov
2008-06-06 2:35 ` Daniel Jacobowitz
2008-05-14 4:26 ` David Miller
2008-05-14 4:30 ` Daniel Jacobowitz
2008-05-14 11:51 ` David Miller
2008-05-14 14:48 ` Daniel Jacobowitz
2008-05-14 17:33 ` David Miller
2008-05-14 18:05 ` Andreas Schwab
2008-05-14 18:09 ` David Miller
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=1210710229.4615.566.camel@localhost.localdomain \
--to=msnyder@specifix.com \
--cc=dje@google.com \
--cc=drow@false.org \
--cc=gdb-patches@sourceware.org \
--cc=ppluzhnikov@google.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