From: Keith M Wesolowski <wesolows@foobazco.org>
To: sparclinux@vger.kernel.org
Subject: Re: mystery backtrace
Date: Wed, 12 May 2004 23:22:54 +0000 [thread overview]
Message-ID: <20040512232254.GA24017@foobazco.org> (raw)
In-Reply-To: <20040512220458.GA4624@amarooas.com.au>
On Thu, May 13, 2004 at 08:04:58AM +1000, Jim Watson wrote:
> this is from openoffice.org 680 on linux sparc
>
> Any advice would be appreciated, is this valid output of the "list" command
> [1], and what can i do next?
>
> 0x00000000 in ?? ()
> (gdb) where
> #0 0x00000000 in ?? ()
> (gdb) list
> 1 /build/buildd/glibc-2.3.2.ds1/build-tree/sparc-libc/csu/crti.S: No
> such file or directory.
> in /build/buildd/glibc-2.3.2.ds1/build-tree/sparc-libc/csu/crti.S
No, the program has for some reason jumped to NULL. You need a full
backtrace if you can get one. If not, your registers are trashed as
well, and you'll have to use breakpoints or some other method to catch
it before it happens. It shows you crti.S because the lowest address
in the binary (closest to the 0x0 shown) is in that standard C runtime.
--
Keith M Wesolowski
prev parent reply other threads:[~2004-05-12 23:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-12 22:04 mystery backtrace Jim Watson
2004-05-12 23:22 ` Keith M Wesolowski [this message]
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=20040512232254.GA24017@foobazco.org \
--to=wesolows@foobazco.org \
--cc=sparclinux@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.