Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Fabian Cenedese <Cenedese@indel.ch>
To: gdb@sources.redhat.com
Subject: Re: Thread-specific breakpoints
Date: Tue, 17 Aug 2004 08:07:00 -0000	[thread overview]
Message-ID: <5.2.0.9.1.20040817084038.01d212a0@NT_SERVER> (raw)
In-Reply-To: <E1BwnBK-0001to-T2@fencepost.gnu.org>

At 15:30 16.08.2004 -0400, Eli Zaretskii wrote:
>> Date: Mon, 16 Aug 2004 16:20:39 +0200
>> From: Fabian Cenedese <Cenedese@indel.ch>
>> >
>> >The closest GDB comes is "break <location> thread <number>".
>> 
>> Yes, that's along the lines I was thinking. And after intense looking I even
>> found it in the manual. I missed it the first time as the break command
>> is explained in 5.1.1 whereas break <location> thread <number> by itself
>> is in 5.4.
>
>The `i' (Info-index) command is your friend.  In an Info browser, type
>"i thread<TAB>" and you will be presented with a list of
>thread-related index entries that are recorded in the manual.  Through
>sheer luck (or maybe something else ;-), the very first entry is
>exactly what you wanted.

Did I mention that I work on Windows? Does the info browser exist there
as well? I'll see if I find something. The printout of the manual is also
quite helpful, you can use a marker :) But of course searching is...
manually :)

Thanks

bye  Fabi  



  reply	other threads:[~2004-08-17  8:07 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-16  7:18 Fabian Cenedese
2004-08-16 13:26 ` Daniel Jacobowitz
2004-08-16 14:20   ` Fabian Cenedese
2004-08-16 14:24     ` Daniel Jacobowitz
2004-08-16 19:30     ` Eli Zaretskii
2004-08-17  8:07       ` Fabian Cenedese [this message]
2004-08-18  3:57         ` Eli Zaretskii
2004-08-18 11:57 Fabian Cenedese
2004-08-26 22:50 ` Paul Breed
2004-08-27  7:37   ` Fabian Cenedese

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=5.2.0.9.1.20040817084038.01d212a0@NT_SERVER \
    --to=cenedese@indel.ch \
    --cc=gdb@sources.redhat.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