public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "vbotton at gmail dot com" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug c++/16752] New: Crash when loading symbols Date: Tue, 25 Mar 2014 13:36:00 -0000 [thread overview] Message-ID: <bug-16752-4717@http.sourceware.org/bugzilla/> (raw) https://sourceware.org/bugzilla/show_bug.cgi?id=16752 Bug ID: 16752 Summary: Crash when loading symbols Product: gdb Version: 7.7 Status: NEW Severity: critical Priority: P2 Component: c++ Assignee: unassigned at sourceware dot org Reporter: vbotton at gmail dot com Created attachment 7490 --> https://sourceware.org/bugzilla/attachment.cgi?id=7490&action=edit The binary on which gdb crash GDB crash when trying to parse the symbols of the attached binary. The backtrace indicate a stack overflow, probably a infinite recursion : #0 0x00000000006f7536 in ?? () #1 0x00000000006f9e67 in ?? () #2 0x00000000006fa561 in ?? () #3 0x00000000006f6c4c in ?? () #4 0x00000000006f76d7 in ?? () #5 0x00000000006f7727 in ?? () #6 0x00000000006f79f9 in ?? () #7 0x00000000006f78ef in ?? () #8 0x00000000006f79f9 in ?? () #9 0x00000000006f6e93 in ?? () #10 0x00000000006f84b5 in ?? () #11 0x00000000006fa59e in ?? () #12 0x00000000006f6c4c in ?? () #13 0x00000000006f76d7 in ?? () #14 0x00000000006f7727 in ?? () #15 0x00000000006f79f9 in ?? () #16 0x00000000006f78ef in ?? () #17 0x00000000006f79f9 in ?? () #18 0x00000000006f6e93 in ?? () #19 0x00000000006f84b5 in ?? () #20 0x00000000006fa59e in ?? () #21 0x00000000006f6c4c in ?? () #22 0x00000000006f76d7 in ?? () #23 0x00000000006f7727 in ?? () #24 0x00000000006f79f9 in ?? () #25 0x00000000006f78ef in ?? () #26 0x00000000006f79f9 in ?? () #27 0x00000000006f6e93 in ?? () #28 0x00000000006f84b5 in ?? () #29 0x00000000006fa59e in ?? () #30 0x00000000006f6c4c in ?? () #31 0x00000000006f76d7 in ?? () #32 0x00000000006f7727 in ?? () #33 0x00000000006f79f9 in ?? () #34 0x00000000006f78ef in ?? () #35 0x00000000006f79f9 in ?? () #36 0x00000000006f6e93 in ?? () #37 0x00000000006f84b5 in ?? () #38 0x00000000006fa59e in ?? () #39 0x00000000006f6c4c in ?? () #40 0x00000000006f76d7 in ?? () #41 0x00000000006f7727 in ?? () #42 0x00000000006f79f9 in ?? () #43 0x00000000006f78ef in ?? () #44 0x00000000006f79f9 in ?? () #45 0x00000000006f6e93 in ?? () #46 0x00000000006f84b5 in ?? () #47 0x00000000006fa59e in ?? () #48 0x00000000006f6c4c in ?? () #49 0x00000000006f76d7 in ?? () #50 0x00000000006f7727 in ?? () #51 0x00000000006f79f9 in ?? () #52 0x00000000006f78ef in ?? () -- You are receiving this mail because: You are on the CC list for the bug.
next reply other threads:[~2014-03-25 13:36 UTC|newest] Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-03-25 13:36 vbotton at gmail dot com [this message] 2014-03-25 21:05 ` [Bug c++/16752] " keiths at redhat dot com 2014-03-26 10:57 ` gbenson at redhat dot com 2014-03-26 14:16 ` gbenson at redhat dot com 2014-03-26 16:23 ` gbenson at redhat dot com 2014-03-28 21:08 ` keiths at redhat dot com 2014-04-15 21:45 ` keiths at redhat dot com 2014-04-19 12:19 ` jia.kai66 at gmail dot com 2014-04-30 18:17 ` adrian.cheater at gmail dot com 2014-04-30 20:39 ` adrian.cheater at gmail dot com 2014-05-01 15:26 ` gbenson at redhat dot com 2014-05-07 15:44 ` gbenson at redhat dot com 2014-05-07 15:45 ` gbenson at redhat dot com 2014-05-07 15:45 ` gbenson at redhat dot com 2014-05-08 9:16 ` gbenson at redhat 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-16752-4717@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: linkBe 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).