From: Andrew Cagney <ac131313@cygnus.com>
To: Paolo Molaro <lupus@ximian.com>
Cc: gdb@sources.redhat.com
Subject: Re: large line number debugging support
Date: Sat, 15 Dec 2001 11:36:00 -0000 [thread overview]
Message-ID: <3C1BA64C.1060104@cygnus.com> (raw)
In-Reply-To: <20011128194140.F22089@lettere.unipd.it>
> Hi.
> I just added support to output stab information in the mono JIT
> compiler: this debugging info is used to debug code generation problems
> and as such the lines in the source code it references are from an
> assembly dump of the CLR programs. For large libraries the assembly
> files can be longer than 2^16 lines and the binary stabs format seems to use
> 16 bits unsigned integers to store line info.
> Is there some kind of know workaround for this problem?
> Splitting the assembly dump would be extremely ugly.
How does dwarf2 go with this? ``gas -gdwarf2'' will select dwarf2
assembler debug info.
Andrew
next prev parent reply other threads:[~2001-12-15 19:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-21 12:33 Paolo Molaro
2001-11-28 10:41 ` Paolo Molaro
2001-12-15 11:36 ` Andrew Cagney [this message]
2001-12-15 12:56 ` Daniel Berlin
2001-12-19 7:21 ` Paolo Molaro
2001-12-19 7:26 ` Joel Brobecker
2001-12-19 11:38 ` Daniel Berlin
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=3C1BA64C.1060104@cygnus.com \
--to=ac131313@cygnus.com \
--cc=gdb@sources.redhat.com \
--cc=lupus@ximian.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