This is the mail archive of the gdb@sources.redhat.com mailing list for the GDB project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: gdb 6.3 misses breakpoint on Linux when inferior does clone()

From: Daniel Jacobowitz <drow at false dot org>
To: Satish Mohan <Satish dot Mohan at Accenia dot com>
Cc: gdb at sources dot redhat dot com
Date: Thu, 26 May 2005 15:43:39 -0400
Subject: Re: gdb 6.3 misses breakpoint on Linux when inferior does clone()
References: <2DC041637C94C64C8039281448B323B2870FBA@abbott.domain.trailerparc.com>

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.  Until it does, there's very
little that GDB can do about this.  It assumes that clone using SIGCHLD
is not sharing a VM space, and clone using a different signal is.

-- 
Daniel Jacobowitz
CodeSourcery, LLC

References:
- gdb 6.3 misses breakpoint on Linux when inferior does clone()
  - From: Satish Mohan

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]