public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Ulrich Weigand <Ulrich.Weigand@de.ibm.com>
To: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>,
	"blarsen@redhat.com" <blarsen@redhat.com>,
	"cel@us.ibm.com" <cel@us.ibm.com>
Cc: "will_schmidt@vnet.ibm.com" <will_schmidt@vnet.ibm.com>
Subject: Re: [PATCH V4] PowerPC, fix gdb.reverse/finish-reverse-bkpt.exp and gdb.reverse/next-reverse-bkpt-over-sr.exp
Date: Wed, 30 Nov 2022 11:30:14 +0000	[thread overview]
Message-ID: <930d9b2f37859733ce04996a1e8cd699bbb59c8a.camel@de.ibm.com> (raw)
In-Reply-To: <015a43bb0dfedfd85f864a2abb9ae005d95103cb.camel@us.ibm.com>

Carl Love <cel@us.ibm.com> wrote:

>+# Move to the function pointer call to void_func so we will use the GEP
>+# to enter void_func and break.
>+set breakloc [gdb_get_line_number "FUNCTION PTR" "$srcfile"]
>+gdb_test "break $breakloc" \
>+    "Breakpoint $decimal at .*$srcfile, line $breakloc\." \
>+    "set breakpoint on funp"
>+gdb_continue_to_breakpoint "funp call" ".*$srcfile:$breakloc.*"

Do we still need this?  In the new source file, there is only
a single call to void_func (via function pointer), so the
tbreak below should already stop there:

> set breakloc [gdb_get_line_number "VOID FUNC" "$srcfile"]
> gdb_test "tbreak void_func" \
>     "Temporary breakpoint $decimal at .*$srcfile, line $breakloc\." \


>+int
>+callee() {		/* ENTER CALLEE */
>+  return myglob++;	/* ARRIVED IN CALLEE */
>+}			/* RETURN FROM CALLEE */

These comment markers seem to be nowhere used.

+   exit (0);      /* end of main */

Comment marker should be all-upper-case like the others.

>+# Move to the function pointer call to the callee call after the function
>+# pointer call to callee to begin the test.  The function pointer call to
>+# callee will use the Global Entry Point on Power.

This comment seems confusing.

Bye,
Ulrich


  reply	other threads:[~2022-11-30 11:30 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-27 16:14 [PATCH] Fix test next-reverse-bkpt-over-sr.exp Carl Love
2022-09-28  7:35 ` Bruno Larsen
2022-11-14 21:05   ` [PATCH] PowerPC, fix gdb.reverse/finish-reverse-bkpt.exp and gdb.reverse/next-reverse-bkpt-over-sr.exp Carl Love
2022-11-21 16:36     ` [PING] " Carl Love
2022-11-22  9:42     ` Bruno Larsen
2022-11-22 16:53       ` Carl Love
2022-11-23  8:44         ` Bruno Larsen
2022-11-23 17:56         ` Ulrich Weigand
2022-11-23 23:33           ` Carl Love
2022-11-28 18:52           ` Carl Love
2022-11-29  8:52             ` Bruno Larsen
2022-11-29 16:50               ` Carl Love
2022-11-29 16:57               ` [PATCH V4] " Carl Love
2022-11-30 11:30                 ` Ulrich Weigand [this message]
2022-12-01  1:33                   ` Carl Love
2022-12-01 15:50                     ` [PATCH V5] " Carl Love
2022-12-01 16:02                       ` 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=930d9b2f37859733ce04996a1e8cd699bbb59c8a.camel@de.ibm.com \
    --to=ulrich.weigand@de.ibm.com \
    --cc=blarsen@redhat.com \
    --cc=cel@us.ibm.com \
    --cc=gdb-patches@sourceware.org \
    --cc=will_schmidt@vnet.ibm.com \
    /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).