Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Yao Qi <yao@codesourcery.com>
To: Jan Kratochvil <jan.kratochvil@redhat.com>,
	Pedro Alves	<palves@redhat.com>
Cc: <gdb-patches@sourceware.org>
Subject: Re: [patchv3] Fix crash on optimized-out entry data values
Date: Mon, 14 Jul 2014 07:02:00 -0000	[thread overview]
Message-ID: <53C32415.90801@codesourcery.com> (raw)
In-Reply-To: <20140711153757.GA452@host2.jankratochvil.net>

On 07/11/2014 11:37 PM, Jan Kratochvil wrote:
> gdb/testsuite/
> 2014-07-09  Jan Kratochvil  <jan.kratochvil@redhat.com>
> 
> 	* gdb.arch/amd64-entry-value-paramref.S: New file.
> 	* gdb.arch/amd64-entry-value-paramref.cc: New file.
> 	* gdb.arch/amd64-entry-value-paramref.exp: New file.
> 	* gdb.arch/amd64-optimout-repeat.S: New file.
> 	* gdb.arch/amd64-optimout-repeat.c: New file.
> 	* gdb.arch/amd64-optimout-repeat.exp: New file.

IWBN to generate .S files by dwarf assembler
(gdb.trace/entry-values.exp, for example).  Although
DW_OP_GNU_entry_value isn't supported in dwarf assembler, it shouldn't
be hard to handle it.

-- 
Yao (齐尧)


  reply	other threads:[~2014-07-14  0:31 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-09 10:33 [patchv2] " 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 [this message]
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
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=53C32415.90801@codesourcery.com \
    --to=yao@codesourcery.com \
    --cc=gdb-patches@sourceware.org \
    --cc=jan.kratochvil@redhat.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