From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 24646 invoked by alias); 18 Mar 2009 04:12:48 -0000 Received: (qmail 24638 invoked by uid 22791); 18 Mar 2009 04:12:47 -0000 X-SWARE-Spam-Status: No, hits=-1.8 required=5.0 tests=AWL,BAYES_00,J_CHICKENPOX_32,J_CHICKENPOX_63,SPF_PASS X-Spam-Check-By: sourceware.org Received: from mail.codesourcery.com (HELO mail.codesourcery.com) (65.74.133.4) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Wed, 18 Mar 2009 04:12:42 +0000 Received: (qmail 2699 invoked from network); 18 Mar 2009 04:12:40 -0000 Received: from unknown (HELO orlando) (pedro@127.0.0.2) by mail.codesourcery.com with ESMTPA; 18 Mar 2009 04:12:40 -0000 From: Pedro Alves To: Paul Pluzhnikov Subject: Re: [patch] Fix a crash when displaying variables from shared ?library. Date: Wed, 18 Mar 2009 04:19:00 -0000 User-Agent: KMail/1.9.10 Cc: Joel Brobecker , gdb-patches@sourceware.org, tromey@redhat.com References: <20090205030257.8A6073A6B7A@localhost> <20090318031516.GL31979@adacore.com> <8ac60eac0903172024g4e381249t43bac2b4c9769a04@mail.gmail.com> In-Reply-To: <8ac60eac0903172024g4e381249t43bac2b4c9769a04@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200903180412.43887.pedro@codesourcery.com> X-IsSubscribed: yes Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org X-SW-Source: 2009-03/txt/msg00360.txt.bz2 On Wednesday 18 March 2009 03:15:16, Joel Brobecker wrote: > If I understand the original issue correctly, we need to restart > the execution of our program in order to demonstrate the issue. > Except with the extended-remote protocol, we can't do that when > using the gdbserver, right? In other words, the "run" command with > target remote doesn't restart the program like in the native case. > So I'd say we kill the test for remote targets. Right, target remote doesn't support "run" at all: (gdb) run The "remote" target does not support "run". Try "help target" or "continue". You'd have to disconnect/kill, and then reconnect perhaps. Maybe using rerun_to_main. On Wednesday 18 March 2009 03:24:04, Paul Pluzhnikov wrote: > On Tue, Mar 17, 2009 at 8:15 PM, Joel Brobecker wrote: > > > If I understand the original issue correctly, we need to restart > > the execution of our program in order to demonstrate the issue. > > Well, not really. You could also > dlopen foo.so > break in foo.so > display something referring to foo.so symbols > dlclose foo.so > re-display > > But writing a portable test for that is harder. Or that. It may not be so hard for most targets we care about. See unload.exp or watchpoint-solib.exp. > Is it as simple as removing changing fail to untested: > > if { [gdb_start_cmd] < 0 } { > - fail "Can't run to main (2)" > + untested "Can't run to main (2)" > return 0 > } Or not that. :-) > > Of course we might just as well skip the test, since it's not going > to test much in that case. Or that is fine with me too. -- Pedro Alves