From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 30247 invoked by alias); 10 Sep 2010 18:32:26 -0000 Mailing-List: contact archer-help@sourceware.org; run by ezmlm Sender: Precedence: bulk List-Post: List-Help: List-Subscribe: List-Id: Received: (qmail 30232 invoked by uid 22791); 10 Sep 2010 18:32:25 -0000 X-SWARE-Spam-Status: No, hits=-6.4 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_HI,SPF_HELO_PASS,T_RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org Date: Fri, 10 Sep 2010 18:32:00 -0000 From: Oleg Nesterov To: Roland McGrath Cc: Jan Kratochvil , utrace-devel@redhat.com, archer@sourceware.org Subject: Re: gdbstub initial code, v7 Message-ID: <20100910182903.GB27699@redhat.com> References: <20100830185850.GA1132@redhat.com> <20100830192040.GA15431@host1.dyn.jankratochvil.net> <20100831072048.GA26362@host1.dyn.jankratochvil.net> <20100902200632.GA23692@redhat.com> <20100903064008.GA16249@host1.dyn.jankratochvil.net> <20100903230957.GC8917@redhat.com> <20100910101452.39015405D5@magilla.sf.frob.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20100910101452.39015405D5@magilla.sf.frob.com> User-Agent: Mutt/1.5.18 (2008-05-17) X-SW-Source: 2010-q3/txt/msg00177.txt.bz2 On 09/10, Roland McGrath wrote: > > > But I meant another case, when the stopped tracee doesn't have siginfo. > > Currently ugdb just sends this signal to tracee, and then it will be > > reported to gdb. Not sure if this is right or not, I can change this. > > (or perhap this doesn't matter, I dunno). > > What do you mean by "doesn't have siginfo"? You mean non-signal stops? Yes. > What non-signal stops does ugdb report? (gdb) interrupt ugdb sets "please stop" flag and does utrace_control(INTERRUPT). However, in unlikely case the tracee can stop before ->report_signal() reporting loop (especially in multitracing case). Or it can be already stopped (note: this needs a separate discussion, currently ugdb intentionally doesn't handle this case). And. With the current implementation, even if the tracee stops after ugdb_report_signal() was called, it doesn't setup ->t_siginfo. IOW. If the tracee actually recieves a signal, then - qXfer:siginfo:read works - "signal SIG" works as expected (delivered to tracee) Otherwise - qXfer:siginfo:read reports E01 - "signal XX" means TXX report. Once again, this can be changed (fixed?), but I am not sure this should be changed. Oleg.