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 symtab/30511] feature: set sysroot and file by default for attached containerized processes Date: Mon, 12 Jun 2023 13:18:44 +0000 [thread overview] Message-ID: <bug-30511-4717-fbmHoobGuL@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-30511-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=30511 --- Comment #9 from Mark Wielaard <mark at klomp dot org> --- (In reply to Tom Tromey from comment #3) > (In reply to Mark Wielaard from comment #2) > > This sounds like a good idea. > > > > Adding myself and Sasha to CC to see how this is done (we would like > > something similar for a "target valgrind", but then set sysroot / and set > > remote exec-file ...). > > Unfortunately this is a different situation. > Probably you should file a separate bug for that one. Done: https://sourceware.org/bugzilla/show_bug.cgi?id=30541 > For this bug, I don't really know how to implement it. > I don't know how to detect if a process needs this treatment. Do you need any detection? Can't you simply always set sysroot /proc/PID/root if it exists? -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2023-06-12 13:18 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-06-04 22:48 [Bug symtab/30511] New: " two at envs dot net 2023-06-05 12:23 ` [Bug symtab/30511] " tromey at sourceware dot org 2023-06-05 12:28 ` mark at klomp dot org 2023-06-06 0:40 ` tromey at sourceware dot org 2023-06-06 21:26 ` two at envs dot net 2023-06-07 8:38 ` sam at gentoo dot org 2023-06-09 21:47 ` tromey at sourceware dot org 2023-06-09 21:52 ` tromey at sourceware dot org 2023-06-10 22:16 ` two at envs dot net 2023-06-11 17:43 ` tromey at sourceware dot org 2023-06-12 13:18 ` mark at klomp dot org [this message] 2023-06-12 13:30 ` mark at klomp dot org
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-30511-4717-fbmHoobGuL@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).