public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: "Satish Mohan" <Satish.Mohan@Accenia.com>
To: "Daniel Jacobowitz" <drow@false.org>
Cc: <gdb@sources.redhat.com>
Subject: RE: gdb 6.3  misses breakpoint on Linux when inferior does clone()
Date: Thu, 26 May 2005 20:02:00 -0000	[thread overview]
Message-ID: <2DC041637C94C64C8039281448B323B2870FC0@abbott.domain.trailerparc.com> (raw)



-----Original Message-----
From: Daniel Jacobowitz [mailto:drow@false.org] 
Sent: Thursday, May 26, 2005 12:44 PM
To: Satish Mohan
Cc: gdb@sources.redhat.com
Subject: Re: gdb 6.3 misses breakpoint on Linux when inferior does clone()

On Thu, May 26, 2005 at 12:40:39PM -0700, Satish Mohan wrote:
> Hi  If the inferior does a clone(...,CLONE_VM,...) on Linux, then gdb
> deletes breakpoints in the child which indirectly affects the parent
> because of CLONE_VM. The following sample code illustrates the
> problem:

The kernel does not provide any interface for GDB to know whether or
not a clone syscall has used CLONE_VM.   

[Satish] Doesn't ptrace(PTRACE_GETREGS,...) provide that information ? Or is that arch. specific ?

Thx
--satish

             reply	other threads:[~2005-05-26 20:02 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-26 20:02 Satish Mohan [this message]
2005-05-26 20:03 ` Daniel Jacobowitz
  -- strict thread matches above, loose matches on Subject: below --
2005-05-31 17:06 tronics93-gdb
2005-06-01 13:23 ` Daniel Jacobowitz
2005-06-11 23:31   ` Mark Kettenis
2005-06-12  0:23     ` Daniel Jacobowitz
2005-05-26 19:40 Satish Mohan
2005-05-26 19:43 ` 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=2DC041637C94C64C8039281448B323B2870FC0@abbott.domain.trailerparc.com \
    --to=satish.mohan@accenia.com \
    --cc=drow@false.org \
    --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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).