linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Kevin Buettner <kev@primenet.com>
To: darkmane@w-link.net,
	LinuxPPC Developers List <linuxppc-dev@lists.linuxppc.org>
Subject: Re: Help w/ gdb
Date: Sun, 16 Jan 2000 09:46:58 -0700	[thread overview]
Message-ID: <1000116164658.ZM13760@saguaro.lan> (raw)
In-Reply-To: Sean Chitwood <darkmane@w-link.net> "Help w/ gdb" (Jan 15, 11:12pm)


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/

  reply	other threads:[~2000-01-16 16:46 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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 [this message]
2000-01-17 22:02     ` Sean Chitwood
2000-02-26 16:35   ` Kevin Buettner
  -- strict thread matches above, loose matches on Subject: below --
2000-01-16 20:41 D.J. Barrow
     [not found] <1000117223224.ZM16757@saguaro.lan>
2000-01-18  0:40 ` Sean Chitwood
2000-01-18  2:04   ` Kevin Buettner
2000-02-16 19:11 Pierre Sarrazin
2000-02-16 19:31 ` Kevin Buettner
2000-02-26 16:23 ` 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=1000116164658.ZM13760@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).