Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Guinevere Larsen <guinevere@redhat.com>
To: Tom Tromey <tom@tromey.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH v3] gdb/testsuite: add test for memory requirements of gcore
Date: Wed, 5 Mar 2025 17:03:31 -0300	[thread overview]
Message-ID: <d743e041-1c34-4114-9a96-a8165a7e0b80@redhat.com> (raw)
In-Reply-To: <87ikoo1wwy.fsf@tromey.com>

On 3/4/25 3:19 PM, Tom Tromey wrote:
>>>>>> "Guinevere" == Guinevere Larsen <guinevere@redhat.com> writes:
> Guinevere> The test runs twice, once with the inferior allocating 4Mb of memory,
> Guinevere> and the other allocating 64Mb. My plan was to find the rate at which
> Guinevere> things increase based on inferior size, and have that tested to ensure
> Guinevere> we're not growing that requirement accidentally, but my testing
> Guinevere> actually showed memory requirements going down as the inferior increases,
> Guinevere> so instead I just hardcoded that we need less than 2Mb for the command,
> Guinevere> and it can be tweaked later if necessary.
>
> This seems fine to me.  I didn't understand why it needed to attach, it
> seems like just running it would be the same?  But also it doesn't
> really matter, considering you've done the work.
>
> Approved-By: Tom Tromey <tom@tromey.com>
>
> thanks,
> Tom
>
I noticed today as I returned from a holiday that I misunderstood the 
issue on v2, so I made this small change to the test, to stop it from 
falling. I'll push the test on friday if there are no comments since I 
think it is a pretty trivial change.

---

diff --git a/gdb/testsuite/gdb.base/gcore-memory-usage.exp 
b/gdb/testsuite/gdb.base/gcore-memory-usage.exp
index 1e31578d4a9..db7f270a5e8 100644
--- a/gdb/testsuite/gdb.base/gcore-memory-usage.exp
+++ b/gdb/testsuite/gdb.base/gcore-memory-usage.exp
@@ -59,7 +59,7 @@ proc run_test {megs} {

         gdb_test "attach $inferior_pid" "Attaching to.*"
         set line [gdb_get_line_number "TAG: BREAK HERE" $::testfile.c]
-       gdb_breakpoint "$line" "break at to known line"
+       gdb_breakpoint "${::srcfile}:$line" "break at to known line"
         gdb_continue_to_breakpoint "continue to known line"

         # Get the important info.

-- 
Cheers,
Guinevere Larsen
She/Her/Hers


  reply	other threads:[~2025-03-05 20:04 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-24 14:04 [PATCH] " Guinevere Larsen
2025-02-24 15:24 ` Tom de Vries
2025-02-24 19:47   ` Guinevere Larsen
2025-02-24 18:21 ` Andrew Burgess
2025-02-24 20:00   ` Guinevere Larsen
2025-02-24 20:18     ` Guinevere Larsen
2025-02-25 13:45 ` [PATCH v2] " Guinevere Larsen
2025-02-26 17:50   ` [PATCH v3] " Guinevere Larsen
2025-03-04 18:19     ` Tom Tromey
2025-03-05 20:03       ` Guinevere Larsen [this message]
2025-03-05 20:21         ` Tom Tromey
2025-03-05 20:39           ` Guinevere Larsen
2025-03-11 16:14     ` Simon Marchi
2025-03-11 16:43       ` Guinevere Larsen

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=d743e041-1c34-4114-9a96-a8165a7e0b80@redhat.com \
    --to=guinevere@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=tom@tromey.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