From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 30636 invoked by alias); 4 Sep 2006 17:59:03 -0000 Received: (qmail 30628 invoked by uid 22791); 4 Sep 2006 17:59:03 -0000 X-Spam-Check-By: sourceware.org Received: from ip-85-160-214-251.eurotel.cz (HELO host0.dyn.jankratochvil.net) (85.160.214.251) by sourceware.org (qpsmtpd/0.31) with ESMTP; Mon, 04 Sep 2006 17:59:01 +0000 Received: from host0.dyn.jankratochvil.net (localhost [127.0.0.1]) by host0.dyn.jankratochvil.net (8.13.8/8.13.7) with ESMTP id k84HwVnE018626; Mon, 4 Sep 2006 19:58:31 +0200 Received: (from jkratoch@localhost) by host0.dyn.jankratochvil.net (8.13.8/8.13.8/Submit) id k84HwRo1018624; Mon, 4 Sep 2006 19:58:27 +0200 Date: Mon, 04 Sep 2006 17:59:00 -0000 From: Jan Kratochvil To: Eli Zaretskii Cc: gdb@sourceware.org Subject: Re: Debugging through exec() (Linux MAY_FOLLOW_EXEC) Message-ID: <20060904175827.GA18513@host0.dyn.jankratochvil.net> References: <20060729185317.GA16200@host0.dyn.jankratochvil.net> <200607312038.k6VKchKj018729@elgar.sibelius.xs4all.nl> <20060805164144.GA23819@host0.dyn.jankratochvil.net> <20060808160113.GC21032@nevyn.them.org> <20060814150628.GA24544@host0.dyn.jankratochvil.net> <20060814213849.GA1433@nevyn.them.org> <20060815142819.GA26405@host0.dyn.jankratochvil.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.2i X-IsSubscribed: yes Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2006-09/txt/msg00027.txt.bz2 On Fri, 18 Aug 2006 14:27:44 +0200, Eli Zaretskii wrote: ... > Thanks for the explanations, but I seem to be dense today, because I > don't get to the cheese yet. > > Perhaps if you could describe a scenario where the current behavior is > inconvenient, and what does your patch change in this respect, I will > understand the issues. I have a Perl script spawning scp(1) in PTY. This scp(1) will not print the progress bar if spawned by this Perl script, it shows it otherwise (it uses isatty() to detect it). I would like to debug scp(1) there as the bug is (apparently) not reproducible when scp(1) is executed standalone. Sure there are many ways how to debug it but I feel this is the right sample problem for "catch exec". Unfortunately that my patch will not provide correct enough debugging state after the "exec" event for the new inferior. Patch needs to be improven. Regards, Jan