From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: David Taylor <dtaylor@emc.com>
Cc: gdb-patches@sourceware.org
Subject: Re: RFA 0/2 fix for bug with large structure offsets
Date: Sun, 23 Nov 2014 19:40:00 -0000 [thread overview]
Message-ID: <20141123194013.GA1620@host2.jankratochvil.net> (raw)
In-Reply-To: <18829.1416329565@usendtaylorx2l>
Hi,
I have posted for this patchset:
https://sourceware.org/bugzilla/show_bug.cgi?id=17520#c1
Fedora carries for it the patchset:
http://pkgs.fedoraproject.org/cgit/gdb.git/tree/gdb-rhbz795424-bitpos-20of25.patch
http://pkgs.fedoraproject.org/cgit/gdb.git/tree/gdb-rhbz795424-bitpos-21of25.patch
http://pkgs.fedoraproject.org/cgit/gdb.git/tree/gdb-rhbz795424-bitpos-22of25.patch
http://pkgs.fedoraproject.org/cgit/gdb.git/tree/gdb-rhbz795424-bitpos-23of25.patch
http://pkgs.fedoraproject.org/cgit/gdb.git/tree/gdb-rhbz795424-bitpos-25of25-test.patch
http://pkgs.fedoraproject.org/cgit/gdb.git/tree/gdb-rhbz795424-bitpos-25of25.patch
http://pkgs.fedoraproject.org/cgit/gdb.git/tree/gdb-rhbz795424-bitpos-lazyvalue.patch
It was concluded that patching it before GDB is switched to C++ would be fragile as there cannot be done easy sanity checking if the inferior types width has not regressed. With C++ one can wrap the offset types into sanity-checked classes with overriden operators.
But the GDB switch to C++ takes too many years.
Jan
next prev parent reply other threads:[~2014-11-23 19:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-18 16:53 David Taylor
2014-11-23 19:40 ` Jan Kratochvil [this message]
2014-12-11 20:26 ` David Taylor
2014-12-12 3:57 ` Yao Qi
2014-12-12 11:15 ` Pedro Alves
2014-12-19 2:00 ` David Taylor
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=20141123194013.GA1620@host2.jankratochvil.net \
--to=jan.kratochvil@redhat.com \
--cc=dtaylor@emc.com \
--cc=gdb-patches@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