Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Tom Tromey <tromey@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: [patch 0/2] DW_OP_call: Re: [patch] Support DW_OP_call2 and DW_OP_call4 (PR 10640)
Date: Mon, 07 Jun 2010 11:56:00 -0000	[thread overview]
Message-ID: <20100607115636.GA24148@host0.dyn.jankratochvil.net> (raw)
In-Reply-To: <20091012210844.GA20340@caradoc.them.org> <m3tyy4pcbw.fsf@fleche.redhat.com>

On Mon, 12 Oct 2009 22:49:23 +0200, Tom Tromey wrote:
> Jan> as GCC discusses its use in PR41343 the patch implements it for GDB.
> 
> Also, I forgot to ask -- why not DW_OP_call_ref as well?

DW_OP_call_ref currently was not requested and it may get more tricky due to
inter-CU references.


On Mon, 12 Oct 2009 23:08:44 +0200, Daniel Jacobowitz wrote:
> I'm confused as to why the "struct symbol" comes into this though.
> We're just using it to look up its DWARF location again.  Can we do
> this directly off the target DIE?  We don't free up the loaded
> .debug_info (partly to support DW_FORM_string).

I was not aware the DIEs are being held allocated for read-in CU.  Fixed the
comment there.


> And we have infrastructure to load a given CU's dies whenever we need them.

It should not be needed when only DW_OP_call{2,4} and not DW_OP_call_ref are
supported.


No regressions on {x86_64,x86_64-m32,i686}-fedora13-linux-gnu.

OK to check-in?


Thanks,
Jan


  parent reply	other threads:[~2010-06-07 11:56 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-20 12:37 Jan Kratochvil
2009-10-12 20:43 ` Tom Tromey
2009-10-12 20:49   ` Tom Tromey
2010-06-07 11:56     ` [patch 1/2] DW_OP_call: Provide per_cu in the batons Jan Kratochvil
2010-06-07 17:44       ` Tom Tromey
2010-06-07 19:44         ` Jan Kratochvil
2010-06-07 11:56     ` Jan Kratochvil [this message]
2010-06-07 11:56     ` [patch 2/2] DW_OP_call: Support DW_OP_call2 and DW_OP_call4 Jan Kratochvil
2010-06-07 18:13       ` Tom Tromey
2010-06-07 20:00         ` Jan Kratochvil
2009-10-12 21:08   ` [patch] Support DW_OP_call2 and DW_OP_call4 (PR 10640) Daniel Jacobowitz

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=20100607115636.GA24148@host0.dyn.jankratochvil.net \
    --to=jan.kratochvil@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=tromey@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