From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gdb-patches-return-64042-listarch-gdb-patches=sources.redhat.com@sourceware.org>
Received: (qmail 28989 invoked by alias); 28 May 2009 13:27:26 -0000
Received: (qmail 28979 invoked by uid 22791); 28 May 2009 13:27:25 -0000
X-SWARE-Spam-Status: No, hits=-1.7 required=5.0 	tests=AWL,BAYES_00,SPF_SOFTFAIL
X-Spam-Check-By: sourceware.org
Received: from mtaout7.012.net.il (HELO mtaout7.012.net.il) (84.95.2.19)     by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Thu, 28 May 2009 13:27:19 +0000
Received: from conversion-daemon.i-mtaout7.012.net.il by i-mtaout7.012.net.il (HyperSendmail v2007.08) id <0KKC00I00VBJ3Z00@i-mtaout7.012.net.il> for gdb-patches@sourceware.org; Thu, 28 May 2009 16:26:54 +0300 (IDT)
Received: from HOME-C4E4A596F7 ([84.228.115.215]) by i-mtaout7.012.net.il (HyperSendmail v2007.08) with ESMTPA id <0KKC00I2WW0RDW50@i-mtaout7.012.net.il>; Thu, 28 May 2009 16:26:54 +0300 (IDT)
Date: Thu, 28 May 2009 13:27:00 -0000
From: Eli Zaretskii <eliz@gnu.org>
Subject: Re: [RFA] Fix troubles with watchpoints in DJGPP
In-reply-to: <000d01c9df77$107f4bd0$317de370$@u-strasbg.fr>
To: Pierre Muller <muller@ics.u-strasbg.fr>
Cc: gdb-patches@sourceware.org
Reply-to: Eli Zaretskii <eliz@gnu.org>
Message-id: <833aaps6ht.fsf@gnu.org>
References: <001401c9de9f$928b9f80$b7a2de80$@u-strasbg.fr> <83ab4ys5zy.fsf@gnu.org> <001b01c9df0d$32609890$9721c9b0$@u-strasbg.fr> <834ov5sknk.fsf@gnu.org> <000d01c9df77$107f4bd0$317de370$@u-strasbg.fr>
X-IsSubscribed: yes
Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-patches.sourceware.org>
List-Subscribe: <mailto:gdb-patches-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-patches/>
List-Post: <mailto:gdb-patches@sourceware.org>
List-Help: <mailto:gdb-patches-help@sourceware.org>, <http://sourceware.org/ml/#faqs>
Sender: gdb-patches-owner@sourceware.org
X-SW-Source: 2009-05/txt/msg00605.txt.bz2

> From: "Pierre Muller" <muller@ics.u-strasbg.fr>
> Cc: <gdb-patches@sourceware.org>
> Date: Thu, 28 May 2009 11:31:22 +0200
> 
> > > > > (bad file descriptor errors when trying to restart
> > > > > a ./gdb executable at level 2, meaning inside another gdb
> > > > > itself being debugged by gdb).
> > 
> > Can you show an example of these ``bad file descriptor errors''?  I
> > don't think I ever saw them.
> 
>   This one is more tricky, I only saw it with 3 levels of gdb.
> And maybe watchpoints were needed too...
>   I will try to find a reproducible way, but it might not be so easy.

Thank you.

>   What I am missing is a FSEXT hook call inside dup 
> so that I know that the return value of dup is used,
> instead with current gdbcom.c code, I will only get a 
> call to dbg_fsext when this handle is closed, but 
> at that point, I would have no idea where this handle is coming from!

But you can set a breakpoint on dup itself, can't you?  Then you will
see both the input descriptor and the one it returns to the caller.