From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.129.124]) by sourceware.org (Postfix) with ESMTPS id E2D583857C5A for ; Wed, 23 Aug 2023 15:26:17 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org E2D583857C5A Authentication-Results: sourceware.org; dmarc=pass (p=none dis=none) header.from=redhat.com Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=redhat.com DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1692804377; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=KOduM8zxLrJAhfkOf9JaW8ToGLhR0UGn1ionchEYNBw=; b=KQw1eoo4YBJWOAwqaTh11CaOAeI1E1h0D4vwNxZYdE/E4fKuIfqANd93R5jHTTcJuAOkw3 Vy6MaFhW3GjklKHJyNEpYD7lrzp4Wj1ax1JMiqoZBxpBbKkGBaTzcZrPBRArS0uqBDP1zc id4VRP4IFg1ta6yep0Be9EAvf7xuCAA= Received: from mail-ed1-f72.google.com (mail-ed1-f72.google.com [209.85.208.72]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.3, cipher=TLS_AES_256_GCM_SHA384) id us-mta-55-V7Y7nkoEPSW88j2P6GtqJA-1; Wed, 23 Aug 2023 11:26:16 -0400 X-MC-Unique: V7Y7nkoEPSW88j2P6GtqJA-1 Received: by mail-ed1-f72.google.com with SMTP id 4fb4d7f45d1cf-5219ceead33so3995028a12.2 for ; Wed, 23 Aug 2023 08:26:16 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1692804374; x=1693409174; h=mime-version:message-id:date:references:in-reply-to:subject:to:from :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=KOduM8zxLrJAhfkOf9JaW8ToGLhR0UGn1ionchEYNBw=; b=QJI9+S1Q6dtoaKMYiC6c65CVCPIzC9Y0IIf4UZ/Ug2BYqsGXra72gTCKpA+OW8XyGs GcUEchNU++vu91Mu+9vn/jA75ydmDvXKWoi+5PWXtwR5iMFONsOTX3+MUvsojpgcw7dr +1HEIxT7QxYzUT680o8la0nTha+4QbVapOTxs2RV0vDjg/5K3SGFeapYpMLNsy1WI2Lv f6Lfdh9orRrw/Ps60GzJ/deWLKRPokOk32czi1Ta6VGTEgU0YPlIqV7WIe1yrvDVvP5b hiImfHfgl492E6fZWt2ec0BtlpJzfQCLoqWcgAhVTTRRWb0qih35WexB+uOD5VZw3gbO oNkA== X-Gm-Message-State: AOJu0YxdJUoYas7Zk4auVFuy1w7+/HsVVQmhxvvpyJJdeP62P4a/kSGv PLwdH9PJWAulgw582gP6ui6VHosKs8h9iiUtBwDfAyYZowF1DtoK/sDvZVWVxAAbD/ZyE4CFQFj b3LZPYQOa/3oDvuk86FKF/HRH7A8E+g== X-Received: by 2002:aa7:d616:0:b0:525:5ed2:abed with SMTP id c22-20020aa7d616000000b005255ed2abedmr9492903edr.30.1692804374416; Wed, 23 Aug 2023 08:26:14 -0700 (PDT) X-Google-Smtp-Source: AGHT+IEZ7hoB7ipFClm20uttxaNhjUiNqbeE7xkGAWqiTISL0NysyYdFkrUA7K6iiM8BDh4Z9O8dAQ== X-Received: by 2002:aa7:d616:0:b0:525:5ed2:abed with SMTP id c22-20020aa7d616000000b005255ed2abedmr9492889edr.30.1692804374158; Wed, 23 Aug 2023 08:26:14 -0700 (PDT) Received: from localhost ([31.111.84.232]) by smtp.gmail.com with ESMTPSA id u2-20020a056402110200b005231e3d89efsm9519865edv.31.2023.08.23.08.26.13 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 23 Aug 2023 08:26:13 -0700 (PDT) From: Andrew Burgess To: Mark Wielaard , gdb-patches@sourceware.org Subject: Re: [PATCH 00/10] Improve GDB/gdbserver experience when using a local gdbserver In-Reply-To: References: Date: Wed, 23 Aug 2023 16:26:12 +0100 Message-ID: <877cplbx0r.fsf@redhat.com> MIME-Version: 1.0 X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain X-Spam-Status: No, score=-5.8 required=5.0 tests=BAYES_00,DKIMWL_WL_HIGH,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,KAM_SHORT,RCVD_IN_DNSWL_NONE,RCVD_IN_MSPIKE_H4,RCVD_IN_MSPIKE_WL,SPF_HELO_NONE,SPF_NONE,TXREP autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on server2.sourceware.org List-Id: Mark Wielaard writes: > Hi Andrew, > > On Wed, 2023-08-16 at 16:54 +0100, Andrew Burgess wrote: >> The goal of this series is to improve the user experience when using a >> local (running on the same machine as GDB) gdbserver. >> >> Outside of testing, there are still plenty of occasions when a user >> can end up running gdbserver on the same machine as GDB, tools like >> valgrind communicate via the remote protocol, as do many simulators >> (other than those built into GDB). >> >> This series includes the following improvements: >> >> 1. Better handling of gdbserver's default executable and arguments. >> This applies to remote gdbservers and local gdbservers, >> >> 2. Allow sysroot 'target:' prefix to be ignored when gdbserver is >> running locally to GDB, and >> >> 3. Allow the user to skip setting 'remote exec-file' if gdbserver is >> running locally to GDB. > > I read through most of this patch series and created a trivial > qDefaultExecAndArgs for vgdb that just returns 'U' and it seems to work > just fine, no more setting of remote exec-file needed \o/ > https://bugs.kde.org/show_bug.cgi?id=473687 Excellent. > I have to think a bit more about qMachineId. > There were also some opinions expressed in this bug: > https://sourceware.org/bugzilla/show_bug.cgi?id=30541 Thanks for the link. I'd not read that. I think the only thing I took from that was that the boot-id that I'm currently using likely isn't going to work w.r.t. containers -- but Thiago Jung Bauermann already pointed that out. We already have some container detection support (at least, I believe that's what it's doing) in linux_nat_target::filesystem_is_local (), so I'm hoping I can use something based off that to extend what I currently have. It's just testing it that's going to slow me down, but I hope to take another pass at it soon. Thanks, Andrew