From: Pedro Alves <pedro@palves.net>
To: Simon Marchi <simark@simark.ca>, gdb-patches@sourceware.org
Subject: Re: [PATCH] gdb.base/execl-update-breakpoints.exp: Don't execl forever
Date: Thu, 9 Jul 2026 19:52:59 +0100 [thread overview]
Message-ID: <056e0d75-8449-4188-a7fb-9896f70a606c@palves.net> (raw)
In-Reply-To: <9043916e-cf6c-4e37-ba48-b59f8b7db081@simark.ca>
On 2026-07-09 19:14, Simon Marchi wrote:
> So the goal is just to have one exec and then exit? Could we just pass
> a regular argument (argv[1]) instead of tweaking argv[0]? Like the
> process could be launched without argument at first, and then it execs
> itself with an argument, and just the presence of that argument would be
> a flag to say "don't re-exec, just exit".
It's not about the exec event, it has to be two separate programs:
# Build two copies of the program, each linked at a different address.
# The address of "main" in the first binary should end up being an
# unmapped address in the second binary.
next prev parent reply other threads:[~2026-07-09 18:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-09 17:58 Pedro Alves
2026-07-09 18:14 ` Simon Marchi
2026-07-09 18:52 ` Pedro Alves [this message]
2026-07-09 19:41 ` Simon Marchi
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=056e0d75-8449-4188-a7fb-9896f70a606c@palves.net \
--to=pedro@palves.net \
--cc=gdb-patches@sourceware.org \
--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