public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "oliver.gerlich at gmx dot de" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug mi/10252] -var-info-path-expression broken with python pretty-printing Date: Thu, 31 Mar 2011 11:12:00 -0000 [thread overview] Message-ID: <bug-10252-4717-Y1zMzQ7l3Y@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-10252-4717@http.sourceware.org/bugzilla/> http://sourceware.org/bugzilla/show_bug.cgi?id=10252 Oliver Gerlich <oliver.gerlich at gmx dot de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |oliver.gerlich at gmx dot | |de -- Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
next parent reply other threads:[~2011-03-30 15:45 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-10252-4717@http.sourceware.org/bugzilla/> 2011-03-31 11:12 ` oliver.gerlich at gmx dot de [this message] 2023-08-31 17:23 ` [Bug varobj/10252] " tromey at sourceware dot org 2023-08-31 19:10 ` tromey at sourceware dot org 2023-08-31 19:11 ` tromey at sourceware dot org 2023-08-31 20:01 ` tromey at sourceware dot org 2023-09-26 15:35 ` tromey at sourceware dot org 2023-09-26 15:36 ` tromey at sourceware dot org 2009-06-07 22:49 [Bug mi/10252] New: " vladimir at codesourcery dot com 2009-06-08 16:03 ` [Bug mi/10252] " tromey at redhat dot com 2009-06-12 22:01 ` tparker at google dot com 2009-06-15 19:26 ` tromey at redhat dot com 2009-10-09 18:29 ` sprigogin at google dot com 2010-03-04 7:29 ` jens dot elmenthaler at verigy dot com 2010-08-02 15:32 ` marc dot khouzam at ericsson 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-10252-4717-Y1zMzQ7l3Y@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).