From: Daniel Jacobowitz <drow@mvista.com>
To: gdb@sources.redhat.com
Subject: Re: Lifetime of local variables
Date: Fri, 12 Apr 2002 16:42:00 -0000 [thread overview]
Message-ID: <20020412194304.B11562@nevyn.them.org> (raw)
In-Reply-To: <86u1qghdp5.fsf@einstein.home-of-linux.org>
On Fri, Apr 12, 2002 at 10:19:50PM +0200, Martin Baulig wrote:
> Hi,
>
> I was recently working a bit on debugging support for C# (using Mono)
> and I need a way to tell GDB about the lifetime of local variables. In
> C#, the JIT engine may decide to store two different variables at the
> same stack offset if they aren't used throughout the whole function.
>
> Now I was wondering how to do this - DWARF 2 already has a
> `DW_AT_begin_scope' but unfortunately no `DW_AT_end_scope' - can we
> add this or something similar as a GNU extension ?
No. I'd strongly object to adding any DWARF-2 tags without at least
discussing them with the DWARF committee (which is quite responsive, I
believe).
Also, I believe that this should be entirely subsumed by .debug_loc.
The first variable's value may no longer be available, but it has not
actually gone out of scope, has it? We should list it but claim that
its value is unavailable.
--
Daniel Jacobowitz Carnegie Mellon University
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2002-04-12 23:42 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-12 16:18 Martin Baulig
2002-04-12 16:42 ` Daniel Jacobowitz [this message]
2002-04-13 4:35 ` Martin Baulig
2002-04-13 5:08 ` Momchil Velikov
2002-04-13 5:42 ` Martin Baulig
2002-04-13 11:32 ` Daniel Jacobowitz
2002-04-13 12:53 ` Martin Baulig
2002-04-13 12:59 ` Daniel Jacobowitz
2002-04-13 13:10 ` Momchil Velikov
2002-04-16 5:56 ` Daniel Berlin
2002-04-16 6:15 ` Daniel Berlin
2002-04-16 15:07 ` Jim Blandy
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=20020412194304.B11562@nevyn.them.org \
--to=drow@mvista.com \
--cc=gdb@sources.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