From: Andreas Schwab <schwab@linux-m68k.org>
To: David Taylor <dtaylor@emc.com>
Cc: Doug Evans <dje@google.com>, nick clifton <nickc@redhat.com>,
binutils@sourceware.org, gcc@gcc.gnu.org,
gdb <gdb@sourceware.org>
Subject: Re: stabs support in binutils, gcc, and gdb
Date: Mon, 14 Jan 2013 22:18:00 -0000 [thread overview]
Message-ID: <m2r4lnxvc8.fsf@igel.home> (raw)
In-Reply-To: <13032.1358189769@usendtaylorx2l> (David Taylor's message of "Mon, 14 Jan 2013 13:56:09 -0500")
David Taylor <dtaylor@emc.com> writes:
> Optimized, -O2.
Then it is expected that dwarf debug is much bigger than stabs debug,
since the latter does not include any of the value tracking capabilities
of dwarf. Without that it is almost impossible for a debugger to
display the true value of local variables.
Andreas.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
next prev parent reply other threads:[~2013-01-14 22:18 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-03 16:22 David Taylor
2013-01-03 16:42 ` Richard Biener
2013-01-03 16:53 ` Joel Brobecker
2013-01-03 16:56 ` nick clifton
2013-01-04 3:31 ` Doug Evans
2013-01-11 14:53 ` David Taylor
2013-01-11 17:41 ` Doug Evans
2013-01-12 1:55 ` Cary Coutant
2013-01-12 2:17 ` Ian Lance Taylor
2013-01-14 16:06 ` Doug Evans
2013-01-14 19:45 ` Cary Coutant
2013-01-14 16:12 ` Doug Evans
2013-01-14 19:49 ` Jan Kratochvil
2013-01-12 13:26 ` Andreas Schwab
2013-01-14 18:57 ` David Taylor
2013-01-14 22:18 ` Andreas Schwab [this message]
2013-01-14 23:41 ` Eric Botcazou
[not found] <12972.1357230104__33958.3243280233$1357230256$gmane$org@usendtaylorx2l>
2013-01-03 17:02 ` Tom Tromey
2013-01-03 20:53 ` David Edelsohn
2013-01-03 21:53 ` Jonas Maebe
2013-01-03 22:02 ` David Edelsohn
2013-01-04 4:12 ` Joel Brobecker
2013-01-04 20:20 ` David Edelsohn
2013-01-05 0:11 ` David Edelsohn
2013-01-05 7:53 ` Joel Brobecker
2013-01-05 13:28 ` David Edelsohn
2013-01-05 14:52 ` Joel Brobecker
2013-01-06 0:26 ` David Edelsohn
2013-01-06 7:00 ` Joel Brobecker
2013-01-08 8:10 ` Joel Brobecker
2013-01-08 14:38 ` David Edelsohn
2013-01-08 14:46 ` Arnaud Charlet
2013-01-08 14:49 ` David Edelsohn
2013-01-08 14:58 ` Arnaud Charlet
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=m2r4lnxvc8.fsf@igel.home \
--to=schwab@linux-m68k.org \
--cc=binutils@sourceware.org \
--cc=dje@google.com \
--cc=dtaylor@emc.com \
--cc=gcc@gcc.gnu.org \
--cc=gdb@sourceware.org \
--cc=nickc@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