From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 24727 invoked by alias); 29 Apr 2010 18:51:12 -0000 Received: (qmail 24709 invoked by uid 22791); 29 Apr 2010 18:51:10 -0000 X-SWARE-Spam-Status: No, hits=-6.9 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_HI,SPF_HELO_PASS,T_RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org Received: from mx1.redhat.com (HELO mx1.redhat.com) (209.132.183.28) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Thu, 29 Apr 2010 18:51:05 +0000 Received: from int-mx08.intmail.prod.int.phx2.redhat.com (int-mx08.intmail.prod.int.phx2.redhat.com [10.5.11.21]) by mx1.redhat.com (8.13.8/8.13.8) with ESMTP id o3TIoxHt019452 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 29 Apr 2010 14:50:59 -0400 Received: from psique.localnet (vpn-224-77.phx2.redhat.com [10.3.224.77]) by int-mx08.intmail.prod.int.phx2.redhat.com (8.13.8/8.13.8) with ESMTP id o3TIowcW023625; Thu, 29 Apr 2010 14:50:59 -0400 From: Sergio Durigan Junior To: gdb@sourceware.org Subject: Re: How to stop gdbserver while it's listening Date: Thu, 29 Apr 2010 18:51:00 -0000 User-Agent: KMail/1.13.2 (Linux/2.6.32.11-99.fc12.x86_64; KDE/4.4.2; x86_64; ; ) Cc: robert song References: In-Reply-To: MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201004291550.57916.sergiodj@redhat.com> X-IsSubscribed: yes Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2010-04/txt/msg00159.txt.bz2 On Monday 26 April 2010 22:56:00, robert song wrote: > During the gdbserver is listening on one TCP port, I can't stop by > directly press Ctrl-C. > But only open another windows and kill this one. > > target> gdbserver :5555 /tmp/helloworld > target> kill -9 `pgrep gdbserver` > > Is it the only way to stop the gdbserver? Hi Robert, Others can correct me if I'm wrong, but this is the only way of killing gdbserver when you are on the target board. Sometimes you just can't open a new terminal, though. In this case, you can also connect to gdbserver from another machine and issue a `monitor exit' command. -- Sergio