Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Andreas Arnez <arnez@linux.vnet.ibm.com>
To: Pedro Alves <palves@redhat.com>
Cc: Luis Machado <lgustavo@codesourcery.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH] bitfield-parent-optimized-out: Fix struct definition
Date: Tue, 15 Nov 2016 19:53:00 -0000	[thread overview]
Message-ID: <m3shqsv7tw.fsf@oc1027705133.ibm.com> (raw)
In-Reply-To: <8fb6af78-a990-f2ee-8844-2042639beea1@redhat.com> (Pedro Alves's	message of "Tue, 15 Nov 2016 18:12:06 +0000")

On Tue, Nov 15 2016, Pedro Alves wrote:

> On 11/11/2016 11:26 PM, Luis Machado wrote:

>> The patch looks good to me, but i'm wondering if Pedro meant for both
>> members to overlap (a union) instead of being two separate members?
>
> Possibly; I don't remember.  If the changed test would still trigger
> the old GDB bug, then I'm fine with the change.

Yes, the bug is triggered both with the old and new version of
bitfield-parent-optimized-out.exp:

  p var.bitfield
  ERROR: Process no longer exists
  UNRESOLVED: gdb.dwarf2/bitfield-parent-optimized-out.exp: p var.bitfield
  ERROR: Couldn't send p var.intfield to GDB.
  UNRESOLVED: gdb.dwarf2/bitfield-parent-optimized-out.exp: p var.intfield

Thanks, pushed.

--
Andreas


      reply	other threads:[~2016-11-15 19:53 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-11 19:37 Andreas Arnez
2016-11-11 23:27 ` Luis Machado
2016-11-15 18:12   ` Pedro Alves
2016-11-15 19:53     ` Andreas Arnez [this message]

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=m3shqsv7tw.fsf@oc1027705133.ibm.com \
    --to=arnez@linux.vnet.ibm.com \
    --cc=gdb-patches@sourceware.org \
    --cc=lgustavo@codesourcery.com \
    --cc=palves@redhat.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