From: John Darrington <john@darrington.wattle.id.au>
To: Tom Tromey <tom@tromey.com>
Cc: John Darrington <john@darrington.wattle.id.au>,
gdb-patches@sourceware.org
Subject: Re: [PATCH 2/4] Add a dwarf unit type to represent 24 bit values.
Date: Wed, 26 Sep 2018 17:42:00 -0000 [thread overview]
Message-ID: <20180926174157.mw5eocxlfmgliua7@jocasta.intra> (raw)
In-Reply-To: <878t4dvuyf.fsf@tromey.com>
[-- Attachment #1: Type: text/plain, Size: 983 bytes --]
After discussion with the gcc folks, it seems that there is an easier
and much simpler solution, which I'm attaching.
J'
On Fri, Sep 07, 2018 at 03:50:00PM -0600, Tom Tromey wrote:
>>>>> "John" == John Darrington <john@darrington.wattle.id.au> writes:
John> * include/dwarf2.h (enum dwarf_unit_type) [DE_EH_PE_udata3]: New member.
John> ---
John> include/dwarf2.h | 1 +
John> 1 file changed, 1 insertion(+)
I'm afraid I didn't look at the earlier discussion of this.
dwarf2.h is canonically maintained in the gcc repository. So, any
change here has to be sent to gcc-patches and be committed there first.
Then the patch can be applied to gdb -- this counts as obvious (IMO).
Tom
--
Avoid eavesdropping. Send strong encrypted email.
PGP Public key ID: 1024D/2DE827B3
fingerprint = 8797 A26D 0854 2EAB 0285 A290 8A67 719C 2DE8 27B3
See http://sks-keyservers.net or any PGP keyserver for public key.
[-- Attachment #2: 0001-GDB-Don-t-abort-if-the-address-size-is-3-bytes.patch --]
[-- Type: text/x-diff, Size: 702 bytes --]
From f2948209c0292d836ade4dda222c1ffe4aa9abe4 Mon Sep 17 00:00:00 2001
From: John Darrington <john@darrington.wattle.id.au>
Date: Wed, 19 Sep 2018 10:28:43 +0200
Subject: [PATCH] GDB: Don't abort if the address size is 3 bytes.
* gdb/dwarf2-frame.c (encoding_for_size): Deal with the case where size == 3.
---
gdb/dwarf2-frame.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/gdb/dwarf2-frame.c b/gdb/dwarf2-frame.c
index 55ab081bff..dfae2aaf97 100644
--- a/gdb/dwarf2-frame.c
+++ b/gdb/dwarf2-frame.c
@@ -1527,6 +1527,7 @@ encoding_for_size (unsigned int size)
{
case 2:
return DW_EH_PE_udata2;
+ case 3:
case 4:
return DW_EH_PE_udata4;
case 8:
--
2.11.0
next prev parent reply other threads:[~2018-09-26 17:42 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-29 14:18 S12Z [new patchset] John Darrington
2018-08-29 14:18 ` [PATCH 1/4] gdb: Add builtin types for 24 bit integers John Darrington
2018-09-07 22:04 ` Tom Tromey
2018-09-08 4:27 ` John Darrington
2018-09-08 5:56 ` Tom Tromey
2018-08-29 14:18 ` [PATCH 3/4] GDB: Add support for 24 bit addresses John Darrington
2018-09-07 22:04 ` Tom Tromey
2018-08-29 14:19 ` [PATCH 2/4] Add a dwarf unit type to represent 24 bit values John Darrington
2018-09-07 21:50 ` Tom Tromey
2018-09-26 17:42 ` John Darrington [this message]
2018-09-27 2:53 ` Simon Marchi
2018-09-27 5:49 ` John Darrington
2018-09-27 17:53 ` Simon Marchi
2018-09-28 16:03 ` John Darrington
2018-08-29 14:19 ` [PATCH 4/4] GDB: New target s12z John Darrington
2018-09-07 22:03 ` Tom Tromey
2018-09-08 4:46 ` John Darrington
2018-09-08 13:16 ` Tom Tromey
2018-09-08 13:21 ` John Darrington
2018-09-07 22:46 ` S12Z [new patchset] Simon Marchi
2018-09-08 4:18 ` John Darrington
2018-09-08 6:30 ` John Darrington
2018-09-08 21:37 ` Simon Marchi
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=20180926174157.mw5eocxlfmgliua7@jocasta.intra \
--to=john@darrington.wattle.id.au \
--cc=gdb-patches@sourceware.org \
--cc=tom@tromey.com \
/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