Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Maik Beckmann <beckmann.maik@googlemail.com>
To: gdb@sourceware.org
Subject: debugging gdb
Date: Mon, 22 Jun 2009 18:48:00 -0000	[thread overview]
Message-ID: <200906222048.02212.Beckmann.Maik@googlemail.com> (raw)

Hello,

gdb-archer segfaults on me at a certain point in my source code.  To give a 
proper bug report I did wanted to get a backtrace.  So I did
  ulimit -c unlimited
to get a core dump.

However, I all I get by running my systems gdb-6.8 on the core file
  gdb --core=core
is
{{{
$ gdb --core=core
GNU gdb 6.8
Copyright (C) 2008 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-unknown-linux-gnu".
(no debugging symbols found)
Core was generated by `/home/maik/abs/gdb-archer/src/gdb-archer/build/gdb/gdb 
--annotate=3 pong'.
Program terminated with signal 11, Segmentation fault.
[New process 21841]
#0  0x0000000000633ff4 in ?? ()
(gdb) bt
#0  0x0000000000633ff4 in ?? ()
(gdb)
}}}

Can you guys give me a hand on how to move forward from here?


Thanks,
-- Maik

PS: I configured archer with
{{{
  export CFLAGS=" -g -O1 "
  export CXXFLAGS=" -g -O1 "
  ../configure --enable-debug \
      --prefix=/usr \
      --disable-nls \
      --mandir=/usr/share/man \
      --disable-werror \
      --infodir=/usr/share/info
}}}
ran make but didn't install it.


             reply	other threads:[~2009-06-22 18:48 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-22 18:48 Maik Beckmann [this message]
2009-06-22 18:53 ` Daniel Jacobowitz
2009-06-22 19:03   ` Maik Beckmann

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=200906222048.02212.Beckmann.Maik@googlemail.com \
    --to=beckmann.maik@googlemail.com \
    --cc=gdb@sourceware.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