Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Robert Schweikert <rjschwei@mindspring.com>
To: gdb@sources.redhat.com
Subject: traceback troubles
Date: Sat, 09 Dec 2000 03:54:00 -0000	[thread overview]
Message-ID: <3A321CD2.98CBC116@mindspring.com> (raw)

Is there a way to figure out where things went wrong with this type of
traceback?

Program terminated with signal 11, Segmentation fault.
#0  0x400035a6 in ?? ()
(gdb) where
#0  0x400035a6 in ?? ()
#1  0x4000bffc in ?? ()
#2  0x40001f69 in ?? ()
#3  0x40001eda in ?? ()

This is version 4.18 of gdb.

The code was compiled with gcc 2.95.2 on RedHat 6.1 without the -g
option. However, shouldn't I still get a stacktrace that at least points
me to the routine where things went wrong. This is C++ code.

Any help is appreciated.

Thanks,
Robert



--
Robert Schweikert                      MAY THE SOURCE BE WITH YOU
rjschwei@mindspring.com                         LINUX




             reply	other threads:[~2000-12-09  3:54 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-12-09  3:54 Robert Schweikert [this message]
2000-12-09  7:02 ` Fernando Nasser
     [not found]   ` <3A32783C.65092D5B@mindspring.com>
2000-12-09 11:52     ` Fernando Nasser

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=3A321CD2.98CBC116@mindspring.com \
    --to=rjschwei@mindspring.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