This is the mail archive of the
gdb@sources.redhat.com
mailing list for the GDB project.
Re: popen
- From: Bruce Korb <bkorb at veritas dot com>
- To: Daniel Jacobowitz <drow at mvista dot com>
- Cc: Bruce Korb <bkorb at gnu dot org>, Chris Hamilton <chamilto at navtechinc dot com>, gdb at sources dot redhat dot com, bkorb at veritas dot com
- Date: Mon, 20 Jan 2003 19:24:57 -0800
- Subject: Re: popen
- Organization: Home
- References: <3E2C6377.5030600@navtechinc.com> <3E2C6A5C.3AA4D0E3@gnu.org> <20030121020051.GA17791@nevyn.them.org>
Daniel Jacobowitz wrote:
>
> On Mon, Jan 20, 2003 at 01:30:04PM -0800, Bruce Korb wrote:
> > Chris Hamilton wrote:
> > >
> > > Bruce,
> > > I came across your September 24th posting about gdb throwing off a
> > > "Cannot find thread 2049" when it hits a popen
> > > (http://sources.redhat.com/ml/insight/2002-q3/msg00185.html).
> > > I'm currently experiencing the same problem in my application, and I was
> > > wondering if you had any advice on how to solve it.
> Popen should not present this problem. I don't know why it does, so we
> need more information.
It seems to occur when using popen, but not when I do all
the fork/exec stuff myself. I'll see if a trivial popen
example duplicates the problem, but I would guess that many
would have complained by now if it were that easy.
> Meanwhile multi-process debugging is forthcoming. The Linux kernel
> patches are already in and I have more GDB patches queued.
Excellent!! Thank you very much!