public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "muhammad_bilal at mentor dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug breakpoints/11568] delete thread-specific breakpoint on the thread exit
Date: Mon, 24 Dec 2012 08:25:00 -0000	[thread overview]
Message-ID: <bug-11568-4717-jM6diOa4ri@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-11568-4717@http.sourceware.org/bugzilla/>

http://sourceware.org/bugzilla/show_bug.cgi?id=11568

--- Comment #2 from bilal <muhammad_bilal at mentor dot com> 2012-12-24 08:25:05 UTC ---
Hi Jan

breakpoint on the specific thread Number is hit on source line of file when
specified thread Number is reached .Exit the thread no exit the breakpoint e.g

if you don,t mention the thread number this break point is always hit when this
particular source line reaches 

you can see on this
http://sourceware.org/gdb/onlinedocs/gdb/Thread_002dSpecific-Breakpoints.html



Thanks
Bilal

-- 
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.


  parent reply	other threads:[~2012-12-24  8:25 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-11568-4717@http.sourceware.org/bugzilla/>
2012-12-24  8:23 ` muhammad_bilal at mentor dot com
2012-12-24  8:25 ` muhammad_bilal at mentor dot com [this message]
2013-07-19  4:06 ` waqas.jamil47 at gmail dot com
2013-08-22  9:50 ` mwaqas at codesourcery dot com
2013-09-17 19:32 ` cvs-commit at gcc dot gnu.org
2013-09-17 19:46 ` palves at redhat dot com
2013-09-17 19:47 ` palves at redhat dot com
2013-10-07 11:00 ` cvs-commit at gcc dot gnu.org
2013-10-07 11:13 ` cvs-commit at gcc dot gnu.org
2013-10-07 11:16 ` palves at redhat dot com

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=bug-11568-4717-jM6diOa4ri@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=gdb-prs@sourceware.org \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).