From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 48831 invoked by alias); 17 Oct 2019 06:19:35 -0000 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 Received: (qmail 48822 invoked by uid 89); 17 Oct 2019 06:19:34 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=4.3 required=5.0 tests=BAYES_50,CHARSET_FARAWAY_HEADER,FREEMAIL_ENVFROM_END_DIGIT,FREEMAIL_FROM,HTML_MESSAGE,SPF_PASS autolearn=no version=3.3.1 spammy=H*c:HHHHH, dose, H*c:PHrt, 163com X-HELO: m13-14.163.com Received: from m13-14.163.com (HELO m13-14.163.com) (220.181.13.14) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Thu, 17 Oct 2019 06:19:33 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=163.com; s=s110527; h=Date:From:Subject:MIME-Version:Message-ID; bh=vYvwD N7Zx77tnmf9+bdWEqlkRqY041oD6fTnQmatVy0=; b=EWyVZ0wU1z9BHai74+0to bhzjJdzYL4SNi3U/BtP2G0BeX+NeXvcxU+ralfV65zI9szERZNmqK18rcHBLCVKi /FH0hJkOg7cAMgyRaMttM52VJlcc/RR8Kg+ajm0nGQB5nASGosowmnwAJ/ATnDxC llcJ6NPqqFqeSYYvH2u2js= Received: from lkang0305$163.com ( [123.125.37.228] ) by ajax-webmail-wmsvr14 (Coremail) ; Thu, 17 Oct 2019 14:19:28 +0800 (CST) Date: Thu, 17 Oct 2019 06:19:00 -0000 From: =?GBK?B?wfW/tQ==?= To: gdb@sourceware.org Subject: gdbserver for arm does not support multi-process debugging MIME-Version: 1.0 Message-ID: <6fea79cd.5d47.16dd85f053a.Coremail.lkang0305@163.com> Content-Type: text/plain; charset=GBK Content-Transfer-Encoding: base64 X-SW-Source: 2019-10/txt/msg00015.txt.bz2 RGVhciBnZGJAc291cmNld2FyZS5vcmcKCgpJIGFtIHJlc2VhcmNoaW5nIHRo ZSBnZGJzZXJ2ZXIncyBzb3VyY2UgY29kZSBmb3IgQVJNLCB3aGF0IGNvbmZ1 c2VkIG1lIGlzIHRoYXQgaXQgZG9lcyBub3Qgc3VwcG9ydCBtdWx0aS1wcm9j ZXNzIHRvIGRlYnVnIHRoZSB0YXJnZXQncyBjaGlsZCBwcm9jZXNzLCBjYXVz ZSBpdCBkb3NlIG5vdCBpbnRlcmVzdGluZyBpbiBQVFJBQ0VfRVZFTlRfRk9S SywgSSBkb24ndCBrbm93IHdoZXRoZXIgaXQncyBhIGJ1ZyBvciBpdCdzIGp1 c3QgYSBmZWF0dXJlIGJ5IGRlc2lnbi4KCgpBcHByZWNpYXRlIHZlcnkgbXVj aCBmb3IgYW55IHJlcGx5IGFuZCB0aGFuayB5b3Ugc28gbXVjaCEKCg== >From gdb-return-47234-listarch-gdb=sources.redhat.com@sourceware.org Thu Oct 17 07:40:41 2019 Return-Path: Delivered-To: listarch-gdb@sources.redhat.com Received: (qmail 96290 invoked by alias); 17 Oct 2019 07:40:41 -0000 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 Delivered-To: mailing list gdb@sourceware.org Received: (qmail 96278 invoked by uid 89); 17 Oct 2019 07:40:41 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-1.9 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_NONE,SPF_PASS autolearn=ham version=3.3.1 spammy=negotiation X-HELO: mail-qk1-f193.google.com Received: from mail-qk1-f193.google.com (HELO mail-qk1-f193.google.com) (209.85.222.193) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Thu, 17 Oct 2019 07:40:40 +0000 Received: by mail-qk1-f193.google.com with SMTP id p4so1012496qkf.5 for ; Thu, 17 Oct 2019 00:40:39 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sifive.com; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=FbHQJrREYeUhxXd1oLBEacex8dR5R4auoSnEU+om52o=; b=E/Ecvpt7gQm60B+sHn43xk9iV+FL4TYAkDjXKLI8Y3n9u+PqKf5JkLow7nXDru5rxb UV6StN6mxteka3hnltqLFhWtNvihiljBz5+psrBrCTkWsfztNi84ownY+86qBUL+j33h URdrvRDzC68/DmMWLgDRrJXjoiI+Vta//Xonp0LTdKGAuiwRSCkLz2YEYoSMla3aGxTY CdD+ifuk0v3HB4/Pz6CC212YBif5cv9vR9crP5cexoh9162aEnkwBLsl38q7+16sY34P t3GJ+EoOzeN7SjuOB71XC17pUGvfemysoywfT5yJKYc69vQKipBNWEOa1oxYPrFMhCkB EZgg== MIME-Version: 1.0 References: In-Reply-To: From: Vincent Chen Date: Thu, 17 Oct 2019 07:40:00 -0000 Message-ID: Subject: Re: RISC-V: Is it reasonable to extend current target_description for KGDB? To: "Maciej W. Rozycki" Cc: Jim Wilson , gdb@sourceware.org, Paul Walmsley Content-Type: text/plain; charset="UTF-8" X-SW-Source: 2019-10/txt/msg00016.txt.bz2 Content-length: 1419 On Wed, Oct 16, 2019 at 9:21 PM Maciej W. Rozycki wrote: > > On Tue, 15 Oct 2019, Jim Wilson wrote: > > > One possible solution is to add a RISC-V specific command to choose > > the register set used for the default p packet. That way, if there > > are problems with adding registers to it, people have the option to > > switch back to the old way. We already have the "set riscv > > use-compressed-breakpoints [auto|on|off]" command. So we could add a > > similar command to choose the number of registers in the default p > > packet, try changing the default to the full 36 register set, and wait > > to see who complains. People that complain can be told about the > > command to switch back to the old 32 (33?) register set. > > There's such a generic command already available: > > (gdb) set tdesc filename ... > > NB, this has nothing to do with the use of `g'/`G' vs `p'/`P' packets, > both use the same register indices; for the overlapping part, that is of > course. Then no heuristics can cover registers outside the range of the > `g'/`G' packets of course, an XML description does have to be provided for > those registers to be recognised. > I understood. From the perspective of flexibility, compatibility and user-friendly, I agree that adding the negotiation support to the kernel is a better way. Thanks to Jim, Pedro, and Macie for your comments. Best regards, Vincent Chen