From: Paolo Molaro <lupus@ximian.com>
To: gdb@sources.redhat.com
Subject: large line number debugging support
Date: Wed, 21 Nov 2001 12:33:00 -0000 [thread overview]
Message-ID: <20011128194140.F22089@lettere.unipd.it> (raw)
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.
A somewhat related problem is symbol file info removal: it's possible to
add a symbol file at runtime inside gdb, but I haven't found a way to
unload it once I need to restart the program (and I need to restart gdb
as well).
I'm not on the list, so please, Cc me on any replies.
Thanks.
lupus
--
-----------------------------------------------------------------
lupus@debian.org debian/rules
lupus@ximian.com Monkeys do it better
WARNING: multiple messages have this Message-ID
From: Paolo Molaro <lupus@ximian.com>
To: gdb@sources.redhat.com
Subject: large line number debugging support
Date: Wed, 28 Nov 2001 10:41:00 -0000 [thread overview]
Message-ID: <20011128194140.F22089@lettere.unipd.it> (raw)
Message-ID: <20011128104100.rdIZ5o18WZPMJYov_lnfifbXU537oiQzFWGHqgILyKo@z> (raw)
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.
A somewhat related problem is symbol file info removal: it's possible to
add a symbol file at runtime inside gdb, but I haven't found a way to
unload it once I need to restart the program (and I need to restart gdb
as well).
I'm not on the list, so please, Cc me on any replies.
Thanks.
lupus
--
-----------------------------------------------------------------
lupus@debian.org debian/rules
lupus@ximian.com Monkeys do it better
next reply other threads:[~2001-11-28 18:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-21 12:33 Paolo Molaro [this message]
2001-11-28 10:41 ` Paolo Molaro
2001-12-15 11:36 ` Andrew Cagney
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=20011128194140.F22089@lettere.unipd.it \
--to=lupus@ximian.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