From: "D.J. Barrow" <barrow_dj@yahoo.com>
To: Kevin Buettner <kev@primenet.com>,
linuxppc-dev <linuxppc-dev@lists.linuxppc.org>
Subject: Re: Help w/ gdb
Date: Sun, 16 Jan 2000 12:41:13 -0800 (PST) [thread overview]
Message-ID: <20000116204113.12942.qmail@web215.mail.yahoo.com> (raw)
It helps gdb a lot not to compile with optimisation.
e.g. compiling -g -O2 on powerpc stops gcc copying
parameters passed in registers onto the stack
to aid debugging, this results in stack traces &
viewing passed in parameters frequently being rubbish.
Mind you in a project as large as mosizza there may be
inline functions which gcc may refuse to compile
without optimisation.
In short if you can compile for debugging without
using -O2 do so or at least try to compile all the
code
of intrest without the -O2 flag.
--- Kevin Buettner <kev@primenet.com> wrote:
>
> On Jan 15, 11:12pm, Sean Chitwood wrote:
>
> > I periodically ask this question here because I
> have never found a
> > more appropriate audience or satisfactory answer.
> >
> > I am attempting to help w/ the mozilla project,
> but I am having
> > little success due to the following problem. When
> I attempt to
> > debug an assert/crash as I bring up the stack
> trace I notice that
> > some of the frames point only to the ending curly
> brace of a
> > function (Not always the one it says is being
> debugged). I cannot
> > examine variables, or learn anything else
> productive about the
> > situation. I realize I am not familiar w/ gdb, I
> am primarily
> > familiar w/ windows GUI based debuggers, so I
> figure I am missing a
> > configuration setting, but for the life of me I
> can't figure out
> > what it is. I do know that I am keeping the
> source and binary files
> > synced, so that shouldn't be it. It seems to load
> the symbols
> > correctly (no complaining about missing symbols),
> butother than that
> > I seem to be clueless.
>
> I think this is a bug in either the linker or in gdb
> itself. (If it's
> the bug I'm thinking of, the bug is actually in the
> linker, but is
> more easily worked around in gdb.) Get the gdb
> sources and take a look
> at config/powerpc/tm-linux.h. Now search for the
> line
>
> #define SOFUN_ADDRESS_MAYBE_MISSING
>
> Is it there? (I'm guessing not.) Try adding the
> above line to
> tm-linux.h and then rebuild gdb.
>
> Let me know if it fixes your problem.
>
> Thanks,
>
> Kevin
>
> --
> Kevin Buettner
> kev@primenet.com, kevinb@cygnus.com
>
>
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next reply other threads:[~2000-01-16 20:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-01-16 20:41 D.J. Barrow [this message]
-- strict thread matches above, loose matches on Subject: below --
2000-02-16 19:11 Help w/ gdb Pierre Sarrazin
2000-02-16 19:31 ` Kevin Buettner
2000-02-26 16:23 ` Kevin Buettner
[not found] <1000117223224.ZM16757@saguaro.lan>
2000-01-18 0:40 ` Sean Chitwood
2000-01-18 2:04 ` Kevin Buettner
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=20000116204113.12942.qmail@web215.mail.yahoo.com \
--to=barrow_dj@yahoo.com \
--cc=kev@primenet.com \
--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).