public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "mark at klomp dot org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/30541] New: Add target valgrind
Date: Mon, 12 Jun 2023 13:14:36 +0000 [thread overview]
Message-ID: <bug-30541-4717@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=30541
Bug ID: 30541
Summary: Add target valgrind
Product: gdb
Version: unknown
Status: NEW
Severity: normal
Priority: P2
Component: gdb
Assignee: unassigned at sourceware dot org
Reporter: mark at klomp dot org
CC: ahajkova at redhat dot com
Target Milestone: ---
Since valgrind 3.21.0 the valgrind gdbserver (or actually vgdb) has a --multi
mode that enables the extended remote protocol. This simplifies the usage of
valgrind with gdb, but still leaves the user having to setup a few things that
gdb could do if it detects/knows the remote target is valgrind.
"target valgrind" would/should do the following:
- set sysroot /
- set remote exec-file $binary (how to know what the local binary file is?)
- target extended-remote | vgdb --multi
- enable stdio/out "sharing" (currently being "eaten" by remote protocol
packets using |)
https://sourceware.org/bugzilla/show_bug.cgi?id=28916
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2023-06-12 13:14 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-12 13:14 mark at klomp dot org [this message]
2023-06-13 17:01 ` [Bug gdb/30541] " tromey at sourceware dot org
2023-06-13 17:03 ` tromey at sourceware dot org
2023-06-15 11:22 ` pedro at palves dot net
2023-06-15 12:54 ` tromey at sourceware dot org
2023-06-15 13:13 ` mark at klomp dot org
2023-06-15 13:31 ` pedro at palves dot net
2023-06-15 15:40 ` pjfloyd at wanadoo dot fr
2023-06-15 17:04 ` pedro at palves dot net
2023-06-20 17:54 ` tromey at sourceware dot org
2023-07-06 15:55 ` tromey at sourceware dot org
2023-07-06 16:44 ` mark at klomp dot org
2023-07-06 17:17 ` sam at gentoo dot org
2023-07-10 21:36 ` tromey at sourceware dot org
2023-07-11 8:18 ` pedro at palves dot net
2023-07-11 8:24 ` pedro at palves dot net
2023-07-11 8:26 ` pedro at palves dot net
2023-07-11 12:23 ` tromey at sourceware dot org
2023-07-11 17:27 ` pedro at palves dot net
2023-07-11 17:29 ` pedro at palves dot net
2023-07-11 18:46 ` tromey at sourceware dot org
2023-07-11 19:44 ` pedro at palves dot net
2023-07-11 19:50 ` pedro at palves dot net
2023-07-11 21:39 ` mark at klomp dot org
2023-07-12 9:05 ` pedro at palves dot net
2023-07-12 10:26 ` pedro at palves dot net
2023-07-12 10:29 ` pedro at palves dot net
2023-07-13 13:38 ` mark at klomp dot org
2023-07-13 13:59 ` mark at klomp dot org
2023-07-13 14:14 ` tromey at sourceware dot org
2023-07-13 14:26 ` mark at klomp dot org
2023-07-13 16:35 ` pedro at palves dot net
2023-07-13 16:38 ` pedro at palves dot net
2023-07-13 17:43 ` pedro at palves dot net
2023-07-14 15:15 ` mark at klomp dot org
2023-08-25 15:50 ` aburgess at redhat dot com
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=bug-30541-4717@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=gdb-prs@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).