public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "cemkalyoncu at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug c++/18129] Segfault when reading symbols
Date: Tue, 17 Mar 2015 20:46:00 -0000	[thread overview]
Message-ID: <bug-18129-4717-FhD1DLHDW3@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-18129-4717@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=18129

--- Comment #4 from Cem Kalyoncu <cemkalyoncu at gmail dot com> ---
I have switched to another computer to get gdb in gdb for backtrace. Here is
the result. It seems like a stack overflow. This gdb version is different: GNU
gdb (GDB) Fedora 7.7.1-21.fc20

...
Reading symbols from ./UnitTest-Scripting...
Program received signal SIGSEGV, Segmentation fault.
0x084bc860 in d_print_comp_inner ()
gdb) bt
#0  0x084bc860 in d_print_comp_inner ()
#1  0x084c122f in d_print_subexpr ()
#2  0x084bc8e9 in d_print_comp_inner ()
#3  0x084bfd22 in d_print_comp ()
#4  0x084be9b5 in d_print_comp_inner ()
#5  0x084bfd22 in d_print_comp ()
#6  0x084bdeaf in d_print_comp_inner ()
#7  0x084bfd22 in d_print_comp ()
#8  0x084be075 in d_print_comp_inner ()
#9  0x084c0ec4 in d_print_cast.isra ()
#10 0x084bf10c in d_print_comp_inner ()
#11 0x084bfd22 in d_print_comp ()
#12 0x084bd60e in d_print_comp_inner ()
#13 0x084c12a3 in d_print_subexpr ()
#14 0x084bc92b in d_print_comp_inner ()
#15 0x084bfd22 in d_print_comp ()
#16 0x084be9b5 in d_print_comp_inner ()
#17 0x084bfd22 in d_print_comp ()
#18 0x084bdeaf in d_print_comp_inner ()
#19 0x084bfd22 in d_print_comp ()
#20 0x084be075 in d_print_comp_inner ()
#21 0x084c0ec4 in d_print_cast.isra ()
#22 0x084bf10c in d_print_comp_inner ()
#23 0x084bfd22 in d_print_comp ()
#24 0x084bd60e in d_print_comp_inner ()
#25 0x084c12a3 in d_print_subexpr ()
#26 0x084bc92b in d_print_comp_inner ()
#27 0x084bfd22 in d_print_comp ()
#28 0x084be9b5 in d_print_comp_inner ()
#29 0x084bfd22 in d_print_comp ()
#30 0x084bdeaf in d_print_comp_inner ()
#31 0x084bfd22 in d_print_comp ()
#32 0x084be075 in d_print_comp_inner ()
#33 0x084c0ec4 in d_print_cast.isra ()
#34 0x084bf10c in d_print_comp_inner ()
#35 0x084bfd22 in d_print_comp ()
#36 0x084bd60e in d_print_comp_inner ()
#37 0x084c12a3 in d_print_subexpr ()
#38 0x084bc92b in d_print_comp_inner ()
#39 0x084bfd22 in d_print_comp ()
---Type <return> to continue, or q <return> to quit---
#40 0x084be9b5 in d_print_comp_inner ()
#41 0x084bfd22 in d_print_comp ()
#42 0x084bdeaf in d_print_comp_inner ()
#43 0x084bfd22 in d_print_comp ()
....

-- 
You are receiving this mail because:
You are on the CC list for the bug.


  parent reply	other threads:[~2015-03-17 19:31 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-15  7:59 [Bug c++/18129] New: " cemkalyoncu at gmail dot com
2015-03-16  9:10 ` [Bug c++/18129] " cemkalyoncu at gmail dot com
2015-03-17 16:50 ` keiths at redhat dot com
2015-03-17 19:31 ` cemkalyoncu at gmail dot com
2015-03-17 20:46 ` cemkalyoncu at gmail dot com [this message]
2015-03-18 10:50 ` keiths at redhat dot com
2015-04-20 17:59 ` pageexec at gmail dot com

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=bug-18129-4717-FhD1DLHDW3@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=gdb-prs@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).