From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Doug Evans <dje@google.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [patch] Fix DW_OP_call2 and DW_OP_call4 for max-cache-age 0 #2
Date: Tue, 19 Jul 2011 20:55:00 -0000 [thread overview]
Message-ID: <20110719202902.GB24651@host1.jankratochvil.net> (raw)
In-Reply-To: <20110713142758.GA5862@host1.jankratochvil.net>
On Wed, 13 Jul 2011 16:27:59 +0200, Jan Kratochvil wrote:
> gdb/
> 2011-07-13 Jan Kratochvil <jan.kratochvil@redhat.com>
>
> Fix crash if referenced CU is aged out.
> * dwarf2loc.c (per_cu_dwarf_call): New variable back_to, use to for
> xfree of block.data.
> (indirect_pieced_value): New variable back_to, use to for xfree of
> baton.data.
> (dwarf2_compile_expr_to_ax): New variable back_to, use to for xfree of
> block.data.
> * dwarf2read.c (dwarf2_find_base_address): New prototype.
> (load_cu): New function from ...
> (dw2_do_instantiate_symtab): ... the code here ...
> (process_full_comp_unit): ... and here.
> (dwarf2_fetch_die_location_block): Call load_cu first. Call xmemdup on
> retval.data.
>
> gdb/testsuite/
> 2011-07-13 Jan Kratochvil <jan.kratochvil@redhat.com>
>
> * gdb.dwarf2/dw2-op-call.exp (maintenance set dwarf2 max-cache-age 0):
> New.
> * gdb.dwarf2/implptr.exp: Likewise.
Checked in:
http://sourceware.org/ml/gdb-cvs/2011-07/msg00166.html
Thanks,
Jan
next prev parent reply other threads:[~2011-07-19 20:29 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-23 18:50 [patch] Fix DW_OP_call2 and DW_OP_call4 for max-cache-age 0 Jan Kratochvil
2010-08-23 19:30 ` Doug Evans
2010-09-02 17:13 ` Jan Kratochvil
2010-09-02 19:33 ` Doug Evans
2011-07-13 15:21 ` [patch] Fix DW_OP_call2 and DW_OP_call4 for max-cache-age 0 #2 Jan Kratochvil
2011-07-19 20:55 ` Jan Kratochvil [this message]
2010-09-03 15:42 ` [patch] Fix DW_OP_call2 and DW_OP_call4 for max-cache-age 0 Tom Tromey
2010-09-03 16:14 ` Jan Kratochvil
2010-09-03 18:06 ` Doug Evans
2010-09-06 11:29 ` Jan Kratochvil
2010-09-06 22:29 ` Doug Evans
2010-09-08 12:26 ` Tom Tromey
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=20110719202902.GB24651@host1.jankratochvil.net \
--to=jan.kratochvil@redhat.com \
--cc=dje@google.com \
--cc=gdb-patches@sourceware.org \
/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).