Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Guinevere Larsen <guinevere@redhat.com>
To: Andrew Burgess <aburgess@redhat.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH] gdb/testsuite: add test for memory requirements of gcore
Date: Mon, 24 Feb 2025 17:18:51 -0300	[thread overview]
Message-ID: <c1bbb0d6-5653-4ba2-be39-89f4908af2d5@redhat.com> (raw)
In-Reply-To: <d451cc22-611d-43a2-9f72-641acd348e0b@redhat.com>

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

On 2/24/25 5:00 PM, Guinevere Larsen wrote:
>> If there was no argument passing here then I'd say you should be using
>> spawn_wait_for_attach.  But that doesn't support argument passing...
>>
>> ... however, if you read that proc (and its helper proc) you'll see some
>> comments that suggest using eval/exec like you do are not the right
>> choice.
>>
>> So maybe we should either extend (somehow) spawn_wait_for_attach to
>> allow argument passing, or write something like spawn_wait_for_attach
>> that handles arguments?
>
> If I found the correct documentation page, I think it shouldn't be 
> hard to extend spawn_wait_for_attach to handle arguments. And using 
> optional arguments, it should be a  very minor patch, so I'll see what 
> I can cook up.
>
> Thanks for the pointer, this definitely sounds like a better solution.

Actually, scratch that, we don't *need* to extend spawn_wait_for_attach. 
We can just give it a list with one element: "$::binfile $megs". So I'll 
definitely go this route.

I can add a convenience function to handle this anyway, if you'd prefer, 
though

-- 
Cheers,
Guinevere Larsen
She/Her/Hers

[-- Attachment #2: Type: text/html, Size: 1874 bytes --]

  reply	other threads:[~2025-02-24 20:19 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-24 14:04 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 [this message]
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
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=c1bbb0d6-5653-4ba2-be39-89f4908af2d5@redhat.com \
    --to=guinevere@redhat.com \
    --cc=aburgess@redhat.com \
    --cc=gdb-patches@sourceware.org \
    /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