From: Yao Qi <qiyaoltc@gmail.com>
To: David Taylor <dtaylor@emc.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH v2] Support structure offsets that are 512K bytes or larger.
Date: Fri, 10 Jun 2016 08:54:00 -0000 [thread overview]
Message-ID: <8637olv2yc.fsf@gmail.com> (raw)
In-Reply-To: <1419.1464988584@usendtaylorx2l> (David Taylor's message of "Fri, 03 Jun 2016 17:16:24 -0400")
David Taylor <dtaylor@emc.com> writes:
Hi David,
> No regressions on x86-64 GNU/Linux.
I rebuild native i686-w64-mingw32 gdb with your patch, the build is
OK. The patch is good to me, some nits below. You can push it in if no
other comments in 3~4 days.
> * c-typeprint.c (c_type_print_base): When printing offset, use plongest, not %d.
This line is too long.
> @@ -723,11 +723,12 @@ pascal_object_print_value (struct type *type, const gdb_byte *valaddr,
>
> for (i = 0; i < n_baseclasses; i++)
> {
> - int boffset = 0;
> + LONGEST boffset = 0;
> struct type *baseclass = check_typedef (TYPE_BASECLASS (type, i));
> const char *basename = type_name_no_tag (baseclass);
> const gdb_byte *base_valaddr = NULL;
> - int thisoffset;
> + LONGEST thisoffset;
> + volatile struct gdb_exception ex; /* XXX */
'ex' is not used at all.
> diff --git a/gdb/testsuite/gdb.base/offsets.c b/gdb/testsuite/gdb.base/offsets.c
> new file mode 100644
> index 0000000..4923d33
> --- /dev/null
> +++ b/gdb/testsuite/gdb.base/offsets.c
> @@ -0,0 +1,28 @@
> +/* This testcase is part of GDB, the GNU debugger.
> +
> + Copyright 2015 Free Software Foundation, Inc.
2014 - 2016 [we start from 2014 because the test was posted in 2014]
> diff --git a/gdb/testsuite/gdb.base/offsets.exp b/gdb/testsuite/gdb.base/offsets.exp
> new file mode 100644
> index 0000000..42c0c5d
> --- /dev/null
> +++ b/gdb/testsuite/gdb.base/offsets.exp
> @@ -0,0 +1,45 @@
> +# Test big offsets
> +
> +# Copyright (c) 2015 Free Software Foundation, Inc.
2014 - 2016
--
Yao (齐尧)
next prev parent reply other threads:[~2016-06-10 8:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-03 21:16 David Taylor
2016-06-10 8:54 ` Yao Qi [this message]
2016-06-17 20:41 ` taylor, david
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=8637olv2yc.fsf@gmail.com \
--to=qiyaoltc@gmail.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