From: Andreas Schwab <schwab@suse.de>
To: Andrew Burgess <aburgess@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH 1/2] gdb: fix 'list' for multiple source file results
Date: Tue, 18 Nov 2025 11:42:43 +0100 [thread overview]
Message-ID: <mvmbjkz4o64.fsf@suse.de> (raw)
In-Reply-To: <9998f4f077aa5ea8ce683a78714ecd760bd3381c.1763461561.git.aburgess@redhat.com> (Andrew Burgess's message of "Tue, 18 Nov 2025 10:28:52 +0000")
On Nov 18 2025, Andrew Burgess wrote:
> +remote_exec build "cp \"$srcdir/$subdir/$srcfile\" \"$file_a\""
> +remote_exec build "cp \"$srcdir/$subdir/$srcfile\" \"$file_b\""
> +remote_exec build "sed -i -e \"s/value_to_return/3/\" \"$file_a\""
> +remote_exec build "sed -i -e \"s/value_to_return/-3/\" \"$file_b\""
If you combine the cp and sed commands then you don't need the
nonportable -i option.
--
Andreas Schwab, SUSE Labs, schwab@suse.de
GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7
"And now for something completely different."
next prev parent reply other threads:[~2025-11-18 10:43 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-18 10:28 [PATCH 0/2] Fix regression in 'list' command Andrew Burgess
2025-11-18 10:28 ` [PATCH 1/2] gdb: fix 'list' for multiple source file results Andrew Burgess
2025-11-18 10:42 ` Andreas Schwab [this message]
2025-11-18 14:28 ` Andrew Burgess
2025-11-18 10:28 ` [PATCH 2/2] gdb: display a symbol more often in multi-file list output Andrew Burgess
2025-11-19 10:32 ` [PATCHv2 0/2] Fix regression in 'list' command Andrew Burgess
2025-11-19 10:32 ` [PATCHv2 1/2] gdb: fix 'list' for multiple source file results Andrew Burgess
2025-12-04 16:48 ` Tom Tromey
2025-12-05 10:50 ` Andrew Burgess
2025-12-04 20:18 ` Kevin Buettner
2025-12-05 7:14 ` Eli Zaretskii
2025-11-19 10:32 ` [PATCHv2 2/2] gdb: display a symbol more often in multi-file list output Andrew Burgess
2025-12-04 16:53 ` Tom Tromey
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=mvmbjkz4o64.fsf@suse.de \
--to=schwab@suse.de \
--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