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.133.124]) by sourceware.org (Postfix) with ESMTPS id 9A54E3858D33 for ; Thu, 27 Apr 2023 13:00:26 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org 9A54E3858D33 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=1682600426; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=TkTAfN2nKQNYEMsDAilxhpkmVfeXi9rX1AlAaFETWLE=; b=Rk2IHzuf3yRevib7afAwJqlfqilCIHClKiLZVW2Yl+ERneUDllQ5rz7318p3PmpubUpNj2 7wC/0Xf7e7PELqg+U7WCFYBmUNEcdz2oXDD2HIlNinf68ynvRiOR7o5dvNW1ts7MeaFsCY cvnEUlz+7CZgGBBZkROeXwmT1vo91Go= Received: from mail-wm1-f69.google.com (mail-wm1-f69.google.com [209.85.128.69]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.3, cipher=TLS_AES_256_GCM_SHA384) id us-mta-192-uYOXZcoOMsyNLJj7UC5QXQ-1; Thu, 27 Apr 2023 09:00:23 -0400 X-MC-Unique: uYOXZcoOMsyNLJj7UC5QXQ-1 Received: by mail-wm1-f69.google.com with SMTP id 5b1f17b1804b1-3f16ef3be6eso51837435e9.3 for ; Thu, 27 Apr 2023 06:00:20 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1682600419; x=1685192419; h=mime-version:message-id:date:references:in-reply-to:subject:cc:to :from:x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=TkTAfN2nKQNYEMsDAilxhpkmVfeXi9rX1AlAaFETWLE=; b=XuQVpEBPuL7C4OJYkKLRq0sDViUEyZMuYybOiE+y2JjM0StvF2P5E1gSBcuQI2lZhK M3xNWiG/2vX5Gz/PzJCOETmukf3hkEb1Q29OIZF5DK+DGYMqSWEaI3JHYSChXudTLxNb EYE7FHFTS8F+95MY2grwVIiRcz+vX4VwIdrkp06/BleOhxk/aJu4T3JPDFqgq02LRR75 9zaKTqRhdKFmGC0P6iad8KwMHEh1kWeVwLxY4YefTeV9MpazNdPUWsW4zS7SEj62lozJ cwxTo9KuTMnwotQ/rdoRQ04428jluTftFW1jerIJdW9srFkT0zxuaKk7d+AVgetQ5i5Y slLg== X-Gm-Message-State: AC+VfDx96qsOqREE9X59QDhvNTF5F7yvBBDfOaaGC/uEGbsJ+b8vsWg3 aLBe2oaf7vr/1dmM9MlhEMTB4BgNdkevzD42W5Lx/WoUoYyv7EZFCq9/F3wtq9yHU6Sodq+ohsy 3XnOLk0Rc46eMYSV3WYHaA9NMb/qm9Q== X-Received: by 2002:a05:600c:2046:b0:3f1:9503:4db0 with SMTP id p6-20020a05600c204600b003f195034db0mr1496563wmg.13.1682600419471; Thu, 27 Apr 2023 06:00:19 -0700 (PDT) X-Google-Smtp-Source: ACHHUZ6w2dsatv4IzdamQdX3681aRTBceIy9m2nbsn1D90qSZtODZgGwKRVQj1IFqL2GrslEMNWExw== X-Received: by 2002:a05:600c:2046:b0:3f1:9503:4db0 with SMTP id p6-20020a05600c204600b003f195034db0mr1496543wmg.13.1682600419161; Thu, 27 Apr 2023 06:00:19 -0700 (PDT) Received: from localhost (11.72.115.87.dyn.plus.net. [87.115.72.11]) by smtp.gmail.com with ESMTPSA id c10-20020a7bc2aa000000b003f080b2f9f4sm24400053wmk.27.2023.04.27.06.00.18 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Thu, 27 Apr 2023 06:00:18 -0700 (PDT) From: Andrew Burgess To: Eli Zaretskii Cc: gdb-patches@sourceware.org Subject: Re: [PATCH] gdb/doc: extend the documentation of the jump command In-Reply-To: <831qk9xmwy.fsf@gnu.org> References: <4da5caec8b9bba91ffc25349e86bc99797f4c9e2.1682352919.git.aburgess@redhat.com> <831qk9xmwy.fsf@gnu.org> Date: Thu, 27 Apr 2023 14:00:17 +0100 Message-ID: <87fs8lbhum.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.6 required=5.0 tests=BAYES_00,DKIMWL_WL_HIGH,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_NONE,RCVD_IN_MSPIKE_H2,SPF_HELO_NONE,SPF_NONE,TXREP,T_SCC_BODY_TEXT_LINE 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: Eli Zaretskii writes: >> Cc: Andrew Burgess >> Date: Mon, 24 Apr 2023 17:15:38 +0100 >> From: Andrew Burgess via Gdb-patches >> >> This commit addresses PR gdb/7946. While checking for bugs relating >> to the jump command I noticed a long standing bug that points out a >> deficiency with GDB's documentation of the jump command. >> >> The bug points out that 'jump 0x...' is not always the same as 'set >> $pc = 0x...' and then 'continue'. Writing directly to the $pc >> register does not update any auxiliary state, e.g. $npc on SPARC, >> while using 'jump' does. >> >> It felt like this would be an easy issue to address by adding a >> paragraph to the docs, so I took a stab at writing something suitable. > > Thanks, this is fine. > > Approved-By: Eli Zaretskii Pushed. Thanks, Andrew