public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Stephan Rohr <stephan.rohr@intel.com>
To: gdb-patches@sourceware.org
Cc: tom@tromey.com, simark@simark.ca, "Rohr,
	Stephan" <stephan.rohr@intel.com>
Subject: [PATCH v2 0/1] gdb/dwarf2: Fix 'rw_pieced_value' for values casted to different type.
Date: Tue, 25 Oct 2022 15:42:06 +0200	[thread overview]
Message-ID: <20221025134207.1548919-1-stephan.rohr@intel.com> (raw)

From: "Rohr, Stephan" <stephan.rohr@intel.com>

Hi all,

this is the second version of my patch.  Changes since v1:

  * Remove the 'internal_error' call in 'rw_pieced_value' if an object's
  'type' and 'enclosing_type' are  not idential.
  * Added additional test cases.

The discussion for v1 can be found at:
https://sourceware.org/pipermail/gdb-patches/2022-October/192547.html

I appreciate your feedback.

Thanks
Stephan

Rohr, Stephan (1):
  gdb/dwarf2: Fix 'rw_pieced_value' for values casted to different type.

 gdb/dwarf2/expr.c                       |  3 --
 gdb/testsuite/gdb.dwarf2/shortpiece.exp | 50 ++++++++++++++++++++++++-
 2 files changed, 49 insertions(+), 4 deletions(-)

-- 
2.25.1

Intel Deutschland GmbH
Registered Address: Am Campeon 10, 85579 Neubiberg, Germany
Tel: +49 89 99 8853-0, www.intel.de <http://www.intel.de>
Managing Directors: Christin Eisenschmid, Sharon Heck, Tiffany Doon Silva  
Chairperson of the Supervisory Board: Nicole Lau
Registered Office: Munich
Commercial Register: Amtsgericht Muenchen HRB 186928


             reply	other threads:[~2022-10-25 13:42 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-25 13:42 Stephan Rohr [this message]
2022-10-25 13:42 ` [PATCH v2 1/1] " Stephan Rohr
2022-11-10  7:58   ` Rohr, Stephan
2022-11-10 15:06   ` Simon Marchi
2022-12-08 11:46     ` Rohr, Stephan
2022-12-21 13:12     ` Rohr, Stephan

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=20221025134207.1548919-1-stephan.rohr@intel.com \
    --to=stephan.rohr@intel.com \
    --cc=gdb-patches@sourceware.org \
    --cc=simark@simark.ca \
    --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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).