public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Aditya Kamath1 <Aditya.Kamath1@ibm.com>
To: Ulrich Weigand <Ulrich.Weigand@de.ibm.com>,
	"gdb-patches@sourceware.org" <gdb-patches@sourceware.org>,
	"simark@simark.ca" <simark@simark.ca>
Cc: Sangamesh Mallayya <sangamesh.swamy@in.ibm.com>
Subject: Re: [PATCH] Modify altivec-regs.exp testcase for AIX
Date: Mon, 17 Oct 2022 06:51:17 +0000	[thread overview]
Message-ID: <CH2PR15MB3544A0712AD4651EF81B3D2DD6299@CH2PR15MB3544.namprd15.prod.outlook.com> (raw)
In-Reply-To: <29b4cea4c1b387f0d85e278f565dc084125f041d.camel@de.ibm.com>

Hi Ulrich,

Thank you for the reply. This was useful. While I was exploring other stuff related to this test case,

In the line gdb_continue_to_breakpoint "func2 breakpoint here, first time",


What does "first time" in the command gdb_continue_to_breakpoint here mean?? I can see a marker with name func2 breakpoint.. Does it mean continue to execute till that marker hits for the first time??

I am curious to know it. It will be helpful. Kindly let me know.

Have a nice day ahead.

Thanks and regards,
Aditya.
________________________________
From: Ulrich Weigand <Ulrich.Weigand@de.ibm.com>
Sent: 14 October 2022 18:17
To: gdb-patches@sourceware.org <gdb-patches@sourceware.org>; Aditya Kamath1 <Aditya.Kamath1@ibm.com>; simark@simark.ca <simark@simark.ca>
Cc: Sangamesh Mallayya <sangamesh.swamy@in.ibm.com>
Subject: Re: [PATCH] Modify altivec-regs.exp testcase for AIX

Aditya Kamath1 <Aditya.Kamath1@ibm.com> wrote:

>Please find attached the patch. [See:- 0001-Modify-altivec-regs.exp-
>testcase-for-AIX.patch]

>+if {[istarget "powerpc*-*-aix*"]} then {
>+  gdb_test "next"
>+  gdb_test "next"
>+}

Hard-coding the fact that there need to be exactly
two "next" iterations is not really a good idea.

Usually this is done by placing a marker comment
in the source code at the target location, and
then using something like:

        gdb_breakpoint [gdb_get_line_number "func2 breakpoint here"]
        gdb_continue_to_breakpoint "func2 breakpoint here, first time"

(example from gdb.base/watchpoint.exp).

Bye,
Ulrich


WARNING: multiple messages have this Message-ID
From: Aditya Kamath1 <Aditya.Kamath1@ibm.com>
To: Ulrich Weigand <Ulrich.Weigand@de.ibm.com>,
	"gdb-patches@sourceware.org" <gdb-patches@sourceware.org>,
	"simark@simark.ca" <simark@simark.ca>
Cc: Sangamesh Mallayya <sangamesh.swamy@in.ibm.com>
Subject: Re: [PATCH] Modify altivec-regs.exp testcase for AIX
Date: Mon, 17 Oct 2022 06:51:17 +0000	[thread overview]
Message-ID: <CH2PR15MB3544A0712AD4651EF81B3D2DD6299@CH2PR15MB3544.namprd15.prod.outlook.com> (raw)
Message-ID: <20221017065117.XDnTdbTFzWrspF4tqDkmazQGT9Z46vxRBz7P4ZbdyL0@z> (raw)
In-Reply-To: <29b4cea4c1b387f0d85e278f565dc084125f041d.camel@de.ibm.com>

[-- Attachment #1: Type: text/plain, Size: 1576 bytes --]

Hi Ulrich,

Thank you for the reply. This was useful. While I was exploring other stuff related to this test case,

In the line gdb_continue_to_breakpoint "func2 breakpoint here, first time",


What does "first time" in the command gdb_continue_to_breakpoint here mean?? I can see a marker with name func2 breakpoint.. Does it mean continue to execute till that marker hits for the first time??

I am curious to know it. It will be helpful. Kindly let me know.

Have a nice day ahead.

Thanks and regards,
Aditya.
________________________________
From: Ulrich Weigand <Ulrich.Weigand@de.ibm.com>
Sent: 14 October 2022 18:17
To: gdb-patches@sourceware.org <gdb-patches@sourceware.org>; Aditya Kamath1 <Aditya.Kamath1@ibm.com>; simark@simark.ca <simark@simark.ca>
Cc: Sangamesh Mallayya <sangamesh.swamy@in.ibm.com>
Subject: Re: [PATCH] Modify altivec-regs.exp testcase for AIX

Aditya Kamath1 <Aditya.Kamath1@ibm.com> wrote:

>Please find attached the patch. [See:- 0001-Modify-altivec-regs.exp-
>testcase-for-AIX.patch]

>+if {[istarget "powerpc*-*-aix*"]} then {
>+  gdb_test "next"
>+  gdb_test "next"
>+}

Hard-coding the fact that there need to be exactly
two "next" iterations is not really a good idea.

Usually this is done by placing a marker comment
in the source code at the target location, and
then using something like:

        gdb_breakpoint [gdb_get_line_number "func2 breakpoint here"]
        gdb_continue_to_breakpoint "func2 breakpoint here, first time"

(example from gdb.base/watchpoint.exp).

Bye,
Ulrich


  reply	other threads:[~2022-10-17  6:51 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-14  7:38 Aditya Kamath1
2022-10-14  7:38 ` Aditya Kamath1
2022-10-14 12:47 ` Ulrich Weigand
2022-10-17  6:51   ` Aditya Kamath1 [this message]
2022-10-17  6:51     ` Aditya Kamath1
2022-10-17  9:57     ` Ulrich Weigand
2022-10-17  9:57       ` Ulrich Weigand
2022-10-19  6:00       ` Aditya Kamath1
2022-10-19  6:00         ` Aditya Kamath1
2023-02-23 12:54         ` Aditya Kamath1
2023-02-24 15:37           ` Ulrich Weigand
2023-03-01 13:45             ` Aditya Kamath1
2023-03-03 15:50               ` Ulrich Weigand
2023-03-06  7:49                 ` Aditya Kamath1
2023-03-07  9:56                   ` Ulrich Weigand

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CH2PR15MB3544A0712AD4651EF81B3D2DD6299@CH2PR15MB3544.namprd15.prod.outlook.com \
    --to=aditya.kamath1@ibm.com \
    --cc=Ulrich.Weigand@de.ibm.com \
    --cc=gdb-patches@sourceware.org \
    --cc=sangamesh.swamy@in.ibm.com \
    --cc=simark@simark.ca \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).