public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "tromey at redhat dot com" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug python/11482] Side effect of set print address on python API Date: Wed, 19 May 2010 23:01:00 -0000 [thread overview] Message-ID: <20100519230104.19190.qmail@sourceware.org> (raw) In-Reply-To: <20100409172931.11482.michel.metzger@st.com> ------- Additional Comments From tromey at redhat dot com 2010-05-19 23:01 ------- (In reply to comment #22) > Thanks for the patch. Unfortunately I'm afraid it does work in my case. > Maybe we could use the pointer value as a hash code for Value object > representing pointers? Many values have mutable contents. So we can't really hash on the contents. We could hash on the address, but not all values have addresses, and, bizarrely, I think you can have values with the same address but different contents (if they were read from inferior memory at different times). This is why we ended up going with identity hashing. I realize this is not ideal. In many cases the above considerations do not apply. However, it seems to me that in a specialized case you could pretty easily write a hashable facade that has whatever hash and equality methods you like. -- http://sourceware.org/bugzilla/show_bug.cgi?id=11482 ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
next prev parent reply other threads:[~2010-05-19 23:01 UTC|newest] Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top 2010-04-09 17:29 [Bug python/11482] New: " michel dot metzger at st dot com 2010-04-14 17:05 ` [Bug python/11482] " pmuldoon at redhat dot com 2010-04-14 17:47 ` michel dot metzger at st dot com 2010-04-14 20:05 ` pmuldoon at redhat dot com 2010-04-14 20:21 ` pmuldoon at redhat dot com 2010-04-14 21:07 ` michel dot metzger at st dot com 2010-04-14 21:29 ` pmuldoon at redhat dot com 2010-04-14 23:18 ` tromey at redhat dot com 2010-04-14 23:31 ` pedro at codesourcery dot com 2010-04-14 23:32 ` pedro at codesourcery dot com 2010-04-15 14:35 ` michel dot metzger at st dot com 2010-04-15 14:40 ` pedro at codesourcery dot com 2010-04-15 16:23 ` pmuldoon at redhat dot com 2010-04-15 16:28 ` pmuldoon at redhat dot com 2010-04-17 6:36 ` pmuldoon at redhat dot com 2010-04-19 22:00 ` tromey at redhat dot com 2010-04-21 15:26 ` michel dot metzger at st dot com 2010-04-21 15:27 ` michel dot metzger at st dot com 2010-05-06 13:16 ` pmuldoon at redhat dot com 2010-05-06 13:28 ` pmuldoon at redhat dot com 2010-05-06 13:29 ` pmuldoon at redhat dot com 2010-05-12 20:21 ` tromey at redhat dot com 2010-05-17 9:21 ` pmuldoon at redhat dot com 2010-05-17 9:22 ` pmuldoon at redhat dot com 2010-05-17 9:22 ` pmuldoon at redhat dot com 2010-05-19 14:57 ` michel dot metzger at st dot com 2010-05-19 14:59 ` michel dot metzger at st dot com 2010-05-19 23:01 ` tromey at redhat dot com [this message] 2010-05-20 14:37 ` michel dot metzger at st dot com 2010-06-30 17:37 ` tromey at redhat dot com [not found] <bug-11482-4717@http.sourceware.org/bugzilla/> 2021-01-15 16:09 ` ssbssa at sourceware dot org 2024-06-22 0:24 ` ssbssa at sourceware 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=20100519230104.19190.qmail@sourceware.org \ --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).