Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Doug Evans <dje@google.com>
To: Jan Kratochvil <jan.kratochvil@redhat.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: Tue, 05 Aug 2014 17:16:00 -0000	[thread overview]
Message-ID: <21473.4449.767906.303936@ruffy.mtv.corp.google.com> (raw)
In-Reply-To: <20140722202004.GA14408@host2.jankratochvil.net>

Jan Kratochvil writes:
 > On Tue, 22 Jul 2014 21:19:22 +0200, Pedro Alves wrote:
 > > OK, I've pushed the reversion (without the #if 0 bit) to both master
 > > and 7.8.
 > 
 > Therefore pushed in the fix of read_frame_arg together with the testcase.
 > 	e214cf6c2e05bcfc85dc6f335d8ffdc3629cf0cf
 > and also for 7.8:
 > 	0f9e1204f3de3cbe46a2b9e54049c1df9a5df305
 > 
 > 
 > Jan
 > commit e214cf6c2e05bcfc85dc6f335d8ffdc3629cf0cf
 > Author: Jan Kratochvil <jan.kratochvil@redhat.com>
 > Date:   Tue Jul 22 22:09:35 2014 +0200
 > 
 >     Fix read_frame_arg for optimized-out entry values.
 >     
 >     gdb/
 >     2014-07-22  Jan Kratochvil  <jan.kratochvil@redhat.com>
 >     
 >     	* stack.c (read_frame_arg): Verify value_optimized_out before calling
 >     	value_available_contents_eq.
 >     
 >     gdb/testsuite/
 >     2014-07-22  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.
 >     
 >     Message-ID: <20140720150727.GA18488@host2.jankratochvil.net>
 >     Message-ID: <20140711153757.GA452@host2.jankratochvil.net>

Hi.

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.

(gdb) file testsuite/gdb.arch/amd64-entry-value-paramref
[...]
(top-gdb) bt
#0  internal_error (file=0xa249e8 "../../entry-value/gdb/dwarf2read.c", line=15776, string=0xa28050 "could not find partial DIE 0x%x in cache [from module %s]\n") at ../../entry-value/gdb/utils.c:823
#1  0x00000000006a89cb in find_partial_die (offset=..., offset_in_dwz=0, cu=0x1029370) at ../../entry-value/gdb/dwarf2read.c:15776
#2  0x00000000006a8c9d in fixup_partial_die (part_die=0x103a6f0, cu=0x1029370) at ../../entry-value/gdb/dwarf2read.c:15855
#3  0x0000000000692b49 in scan_partial_symbols (first_die=0x103a690, lowpc=0x7fffffffdb78, highpc=0x7fffffffdb70, need_pc=0, cu=0x1029370) at ../../entry-value/gdb/dwarf2read.c:6567
#4  0x000000000069132a in process_psymtab_comp_unit_reader (reader=0x7fffffffdcc0, info_ptr=0xf6c78c "\002bar", comp_unit_die=0x103a480, has_children=1, data=0x7fffffffdd90) at ../../entry-value/gdb/dwarf2read.c:5913
#5  0x0000000000690662 in init_cutu_and_read_dies (this_cu=0xf5d770, abbrev_table=0x0, use_existing_cu=0, keep=0, die_reader_func=0x690fe2 <process_psymtab_comp_unit_reader>, data=0x7fffffffdd90) at ../../entry-value/gdb/dwarf2read.c:5529
#6  0x00000000006917d0 in process_psymtab_comp_unit (this_cu=0xf5d770, want_partial_unit=0, pretend_language=language_minimal) at ../../entry-value/gdb/dwarf2read.c:5998
#7  0x0000000000692456 in dwarf2_build_psymtabs_hard (objfile=0x101eab0) at ../../entry-value/gdb/dwarf2read.c:6397
#8  0x000000000068d225 in dwarf2_build_psymtabs (objfile=0x101eab0) at ../../entry-value/gdb/dwarf2read.c:4173
#9  0x0000000000554e9d in read_psyms (objfile=0x101eab0) at ../../entry-value/gdb/elfread.c:1363
[...]


  reply	other threads:[~2014-08-05 17:16 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 [this message]
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=21473.4449.767906.303936@ruffy.mtv.corp.google.com \
    --to=dje@google.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