public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "tromey at sourceware dot org" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug gdb/30541] Add target valgrind Date: Thu, 13 Jul 2023 14:14:16 +0000 [thread overview] Message-ID: <bug-30541-4717-IpjaDJgm4l@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-30541-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=30541 --- Comment #28 from Tom Tromey <tromey at sourceware dot org> --- I may not really understand the environment issue. Using Q* to set the environment and the working directory seems clearly better to me, and in fact the only way it can work properly. The problem case is something like: (gdb) set env X y (gdb) start (gdb) add-inferior blah blah (gdb) set env X z (gdb) start Here, we've made 2 inferiors and started them with different environments. The native target can simply pass this stuff to the inferior via ordinary setenv stuff. For remotes, though, the inheritance can only be done once, other inferiors are not fork'd by gdb. If Q* aren't working on the gdb side, let's make a new bug and make it block this one. If they aren't working on the valgrind side, I suggest a valgrind bug instead. A bonus of implementing vFile and Q* in valgrind is that then "target remote | ssh machine vgdb" will work, which seems nice. -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2023-07-13 14:14 UTC|newest] Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-06-12 13:14 [Bug gdb/30541] New: " mark at klomp dot org 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 [this message] 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-IpjaDJgm4l@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: linkBe 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).