From: Kevin Buettner <kev@primenet.com>
To: darkmane@w-link.net
Cc: LinuxPPC Developers List <linuxppc-dev@lists.linuxppc.org>
Subject: Re: Help w/ gdb
Date: Mon, 17 Jan 2000 19:04:16 -0700 [thread overview]
Message-ID: <1000118020416.ZM17186@saguaro.lan> (raw)
In-Reply-To: Sean Chitwood <darkmane@w-link.net> "Re: Help w/ gdb" (Jan 17, 4:40pm)
On Jan 17, 4:40pm, Sean Chitwood wrote:
> Ok, I'm assuming you mean to change the CFLAGS in the Makefile...
> correct? I'll do that tonight and hopefully let you know in th
> emorning....
Yes. (Or whatever variable your Makefile uses to set the -g debugging
flag for the compiler.)
BTW, make sure you specify it as -gdwarf-2 and NOT -gdwarf2. Oddly
enough, these mean completely different things. (The former says to
use the DWARF2 format while the latter says to use the DWARF format at
debugging level 2.)
> Just for my edification, what is the difference between -g and
> -gdwarf-2... I have a bad feeling one produces elf binaries and one
> produces dwarf binaries.... Not that I would know the difference...
ELF binaries are created in both instances. It's the debugging format
which will be different. Many platforms use the stabs debugging
format by default -- I think this is the default format for linux/ppc.
You can explicitly use a different format by using one of the other
-g switches. (-gstabs, -gstabs+, -gdwarf, -gdwarf+, ...)
To be quite honest with you, I haven't checked recently to see which
debug format linux/ppc uses by default or even if DWARF2 will work at
all. But it is something to try. Even if DWARF2 isn't completely
satisfactory for debugging (e.g, it could generate outrageously large
symbolic information), if it addresses the specific problem that you
reported, it'll let me know if it's worth it for you to try a patch
which does a better job of resolving zero-valued N_FUN symbols for the
stabs format.
I noted in another message that there's a patch at the end of
http://sourceware.cygnus.com/ml/gdb/1999-q3/msg00325.html
that you could try, but I doubt that it will apply cleanly. (I think
I have one that should apply cleanly though. But before I send it to
you, I'd like to know the results of your DWARF2 tests.)
Kevin
--
Kevin Buettner
kev@primenet.com, kevinb@cygnus.com
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2000-01-18 2:04 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1000117223224.ZM16757@saguaro.lan>
2000-01-18 0:40 ` Help w/ gdb Sean Chitwood
2000-01-18 2:04 ` Kevin Buettner [this message]
2000-02-16 19:11 Pierre Sarrazin
2000-02-16 19:31 ` Kevin Buettner
2000-02-26 16:23 ` Kevin Buettner
-- strict thread matches above, loose matches on Subject: below --
2000-01-16 20:41 D.J. Barrow
2000-01-15 21:36 Mac-On-Linux Mailing Lists Dan Burcaw
2000-01-16 7:12 ` Help w/ gdb Sean Chitwood
2000-01-16 16:46 ` Kevin Buettner
2000-01-17 22:02 ` Sean Chitwood
2000-02-26 16:35 ` Kevin Buettner
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=1000118020416.ZM17186@saguaro.lan \
--to=kev@primenet.com \
--cc=darkmane@w-link.net \
--cc=linuxppc-dev@lists.linuxppc.org \
/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;
as well as URLs for NNTP newsgroup(s).