All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jim Watson <jim@amarooas.com.au>
To: sparclinux@vger.kernel.org
Subject: mystery backtrace
Date: Wed, 12 May 2004 22:04:58 +0000	[thread overview]
Message-ID: <20040512220458.GA4624@amarooas.com.au> (raw)

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
(gdb)


thanks

jim

[1] Full report follows:

jim@sun:~/680/cppu/unxlngs.pro/bin$ gdb ./testcppu
GNU gdb 2003-09-18-cvs
Copyright 2003 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain
conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show warranty" for details.
This GDB was configured as "sparc-unknown-linux-gnu"...Using host
libthread_db library "/lib/libthread_db.so.1".

(gdb) run
Starting program: /home/jim/680/cppu/unxlngs.pro/bin/testcppu 
[Thread debugging using libthread_db enabled]
[New Thread 16384 (LWP 7542)]

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 16384 (LWP 7542)]
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
(gdb) 

             reply	other threads:[~2004-05-12 22:04 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-12 22:04 Jim Watson [this message]
2004-05-12 23:22 ` mystery backtrace Keith M Wesolowski

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=20040512220458.GA4624@amarooas.com.au \
    --to=jim@amarooas.com.au \
    --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.