From: Daniel Jacobowitz <drow@false.org>
To: "Thomson, Patrick S" <patrick.s.thomson@intel.com>
Cc: gdb@sources.redhat.com
Subject: Re: Implementing dwarf procedures
Date: Thu, 17 Mar 2005 18:10:00 -0000 [thread overview]
Message-ID: <20050317181020.GB9215@nevyn.them.org> (raw)
In-Reply-To: <B6D265BA39581B46A91EA649F0A0460209DD789E@azsmsx407>
On Thu, Mar 17, 2005 at 11:08:02AM -0700, Thomson, Patrick S wrote:
> Howdy Folks,
>
> I'm part of a compiler project that wants to emit
> dwarf procedures and one of the requirements is that
> the output has to be debuggable with gdb.
>
> I thought I read somewhere in the mailing list that
> DW_OP_call4 was currently being worked on, but I can't
> seem to find it again. Is anyone currently working on,
> or is it planned for 6.x to, support dwarf procedures?
>
> I'm already tasked with doing this, so if there is
> existing work, I'd like to be compatible or contribute.
> If not, implement it such that it can be made part of
> the source tree.
I don't know of anyone working on this, FWIW, nor is there any code for
it currently in GDB.
--
Daniel Jacobowitz
CodeSourcery, LLC
prev parent reply other threads:[~2005-03-17 18:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-17 18:08 Thomson, Patrick S
2005-03-17 18:10 ` Daniel Jacobowitz [this message]
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=20050317181020.GB9215@nevyn.them.org \
--to=drow@false.org \
--cc=gdb@sources.redhat.com \
--cc=patrick.s.thomson@intel.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