From: Klaus Zeitler <kzeitler@lucent.com>
To: gdb@sources.redhat.com
Subject: gdb 6.0 backtrace on Solaris 5.8
Date: Wed, 14 Jan 2004 12:25:00 -0000 [thread overview]
Message-ID: <q5g4quyzph4.fsf@lucent.com> (raw)
I'm using gdb 6.0 on solaris 5.8 and I'm having problems with the backtrace
that gdb 6.0 shows. 'bt' sometimes doesn't show all the calls. I've tried
a few small example programs, but couldn't reproduce it there :-(.
Today I tried to look at an emacs (CVS version) crash and here gdb 6.0 refused
to show any backtrace at all:
gdb 6.0 shows:
Program received signal SIGSEGV, Segmentation fault.
0x00000000 in ?? ()
(gdb) bt
#0 0x00000000 in ?? ()
whereas gdb 5.3 shows:
(gdb) bt
#0 0x00000000 in ?? ()
#1 0xfee5e4bc in XRegisterIMInstantiateCallback () from /usr/lib/libX11.so.4
#2 0x00134804 in xim_initialize (dpyinfo=0x81c800,
resource_name=0x7c4154 "emacs")
at /vol/freeware/cvs/emacs/head/emacs/src/xterm.c:8178
#3 0x0013aba0 in x_term_init (display_name=1618729156, xrm_option=0x0,
resource_name=0x7c4154 "emacs")
at /vol/freeware/cvs/emacs/head/emacs/src/xterm.c:10604
#4 0x00146af8 in Fx_open_connection (display=1618729156,
xrm_string=542359556, must_succeed=542359604)
at /vol/freeware/cvs/emacs/head/emacs/src/xfns.c:4183
#5 0x0023cec8 in Ffuncall (nargs=4, args=0xffbed3d8)
at /vol/freeware/cvs/emacs/head/emacs/src/eval.c:2735
#6 0x0029e450 in Fbyte_code (bytestr=1618727748, vector=-2140932608,
maxdepth=6) at /vol/freeware/cvs/emacs/head/emacs/src/bytecode.c:689
#7 0x0023b60c in Feval (form=-1603144640)
at /vol/freeware/cvs/emacs/head/emacs/src/eval.c:2086
#8 0x00267160 in readevalloop (readcharfun=542497612, stream=0x533f18,
sourcename=1619044260, evalfun=0x23af08 <Feval>, printflag=0,
unibyte=542359556, readfun=542359556)
at /vol/freeware/cvs/emacs/head/emacs/src/lread.c:1376
#9 0x002656c0 in Fload (file=1619044260, noerror=542359556,
nomessage=542359604, nosuffix=542359556, must_suffix=542359556)
at /vol/freeware/cvs/emacs/head/emacs/src/lread.c:914
#10 0x0023cf68 in Ffuncall (nargs=4, args=0xffbed9e8)
at /vol/freeware/cvs/emacs/head/emacs/src/eval.c:2744
#11 0x0029e450 in Fbyte_code (bytestr=1614584644, vector=-2143511692,
maxdepth=4) at /vol/freeware/cvs/emacs/head/emacs/src/bytecode.c:689
#12 0x0023b60c in Feval (form=-1606640844)
...
Any ideas? Thanks.
Klaus
--
------------------------------------------
| Klaus Zeitler Lucent Technologies |
| Email: kzeitler@lucent.com |
------------------------------------------
---
One way to make your old car run better is to look up the price of a
new model.
next reply other threads:[~2004-01-14 12:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-14 12:25 Klaus Zeitler [this message]
2004-01-14 13:53 ` Daniel Jacobowitz
2004-01-20 13:47 ` Klaus Zeitler
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=q5g4quyzph4.fsf@lucent.com \
--to=kzeitler@lucent.com \
--cc=gdb@sources.redhat.com \
/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