Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: "Maciej W. Rozycki" <macro@mips.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: Support for "break *ADDRESS thread THREADNO"
Date: Tue, 12 Apr 2005 18:13:00 -0000	[thread overview]
Message-ID: <20050412181334.GA2560@nevyn.them.org> (raw)
In-Reply-To: <Pine.LNX.4.61.0504121544140.13777@perivale.mips.com>

On Tue, Apr 12, 2005 at 04:53:55PM +0100, Maciej W. Rozycki wrote:
> Hello,
> 
>  The current version of gdb does not accept the "thread THREADNO" clause 
> for breakpoints at an address.  I'm not sure if that's a bug or feature as 
> the info pages carefully avoid documenting what should happen in this 
> case, referring to source lines instead.
> 
>  Anyway I've found the inability to set up such breakpoints an obstacle, 
> so I've implemented the missing bits for it to work.  Here's the result.  
> I've run-time tested the C language bit only (i.e. c-exp.y), but the other 
> .y changes are essentially the same, so they should work as well.  
> Unfortunately I haven't found a way of testing the Ada part which is 
> significantly different; I hope it's OK.
> 
> 2005-04-12  Maciej W. Rozycki  <macro@mips.com>
> 
> 	* ada-lex.l: Support the "thread THREADNO" clause with breakpoints
> 	at an address.
> 	* c-exp.y (yylex): Likewise.
> 	* f-exp.y (yylex): Likewise.
> 	* jv-exp.y (yylex): Likewise.
> 	* m2-exp.y (yylex): Likewise.
> 	* objc-exp.y (yylex): Likewise.
> 	* p-exp.y (yylex): Likewise.
> 
>  This has been verified for the HEAD version with the test suite for the 
> i386-linux-gnu system natively with no regressions.  Please consider.

No, sorry.  Consider:

(gdb) p *thread
No symbol table is loaded.  Use the "file" command.

After your patch:

(gdb) b *thread
A parse error in expression, near `thread'.

We can get away with this for 'if', because 'if' is a keyword in just
about every language GDB supports, and an unlikely name for a variable.
That's not going to fly for 'thread', however.

-- 
Daniel Jacobowitz
CodeSourcery, LLC


  reply	other threads:[~2005-04-12 18:13 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-12 15:54 Maciej W. Rozycki
2005-04-12 18:13 ` Daniel Jacobowitz [this message]
2005-04-12 18:24   ` Maciej W. Rozycki
2005-04-12 18:51   ` Eli Zaretskii
2005-04-12 18:55     ` Daniel Jacobowitz
2005-04-12 19:05       ` Eli Zaretskii
2005-04-12 19:17         ` Stan Shebs
2005-04-12 19:21           ` Daniel Jacobowitz
2005-04-12 19:22         ` Daniel Jacobowitz
2005-04-13 10:36       ` Maciej W. Rozycki
2005-04-13 12:09         ` Daniel Jacobowitz
2005-04-13 16:05           ` Maciej W. Rozycki
2005-04-13 17:37         ` Eli Zaretskii
2005-04-13 17:41           ` Daniel Jacobowitz

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=20050412181334.GA2560@nevyn.them.org \
    --to=drow@false.org \
    --cc=gdb-patches@sources.redhat.com \
    --cc=macro@mips.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