From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Doug Evans <dje@google.com>
Cc: Pedro Alves <palves@redhat.com>, gdb-patches@sourceware.org
Subject: Re: [commit+7.8] [read_frame_arg patch] Handle partially optimized out values similarly to unavailable values
Date: Thu, 14 Aug 2014 18:25:00 -0000 [thread overview]
Message-ID: <20140814182518.GA29503@host2.jankratochvil.net> (raw)
In-Reply-To: <21473.4449.767906.303936@ruffy.mtv.corp.google.com>
On Tue, 05 Aug 2014 19:16:17 +0200, Doug Evans wrote:
> In trunk I'm seeing amd64-entry-value-paramref.exp fail with a
> gdb internal error. I can debug this further if you need me to.
Yes, please. We probably agree it should be sufficient to send me binaries
built by the testcase.
Thanks,
Jan
next prev parent reply other threads:[~2014-08-14 18:25 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-09 10:33 [patchv2] Fix crash on optimized-out entry data values Jan Kratochvil
2014-07-09 11:52 ` Pedro Alves
2014-07-09 15:31 ` Jan Kratochvil
2014-07-11 16:07 ` [patchv3] " Jan Kratochvil
2014-07-14 7:02 ` Yao Qi
2014-07-14 8:32 ` Jan Kratochvil
2014-07-14 18:12 ` Pedro Alves
2014-07-14 18:47 ` [PATCH] Handle partially optimized out values similarly to unavailable values (Re: [patchv2] Fix crash on optimized-out entry data values) Pedro Alves
2014-07-17 8:04 ` Jan Kratochvil
2014-07-17 8:35 ` Jan Kratochvil
2014-07-17 13:38 ` Pedro Alves
2014-07-20 15:33 ` [read_frame_arg patch] " Jan Kratochvil
2014-07-22 19:33 ` Pedro Alves
2014-07-22 20:21 ` [commit+7.8] [read_frame_arg patch] Handle partially optimized out values similarly to unavailable values Jan Kratochvil
2014-08-05 17:16 ` Doug Evans
2014-08-14 18:25 ` Jan Kratochvil [this message]
2014-07-23 14:26 ` [commit] Remove setting value address for reference entry value target data value Jan Kratochvil
2014-07-24 12:51 ` [PATCH v2] Handle partially optimized out values similarly to unavailable values Pedro Alves
2014-08-15 20:13 ` Jan Kratochvil
2014-08-19 23:36 ` Pedro Alves
2014-08-20 0:55 ` Andrew Pinski
2014-08-20 9:46 ` Pedro Alves
2014-08-20 10:32 ` [PUSHED] value.c (value_contents_bits_eq): Initialize l,h for gcc, -Wall. (was: Re: [PATCH v2] Handle partially optimized out values similarly to unavailable values) Pedro Alves
2014-08-20 16:28 ` Andrew Pinski
2014-08-21 19:57 ` Regression for i686 gdb.dwarf2/pieces-optimized-out.exp [Re: [PATCH v2] Handle partially optimized out values similarly to unavailable values] Jan Kratochvil
2014-08-22 16:20 ` Pedro Alves
2014-08-24 19:56 ` Jan Kratochvil
2014-09-04 11:36 ` [pushed] " Pedro Alves
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=20140814182518.GA29503@host2.jankratochvil.net \
--to=jan.kratochvil@redhat.com \
--cc=dje@google.com \
--cc=gdb-patches@sourceware.org \
--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