public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "keiths at redhat dot com" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug c++/18129] Segfault when reading symbols Date: Tue, 17 Mar 2015 16:50:00 -0000 [thread overview] Message-ID: <bug-18129-4717-wkUAqdo1m2@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-18129-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=18129 Keith Seitz <keiths at redhat dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |keiths at redhat dot com --- Comment #2 from Keith Seitz <keiths at redhat dot com> --- I've downloaded and built your executable from the mercurial sources listed on the bitbucket.org link to sourceforge. Since I do not read Turkish, the only language the build instructions are in, I had to blindly build the library with the build.sh script. Fortunately, that eventually spit out a library, libGGE.a, in the "build" directory. You say, "You may try any unit tests in Testing/Tests/Unit folder after compilation." This directory does not exit anywhere in the tree. "Unit" does not exist, either. I built Tests/test.cpp, though: $ g++ -g -m32 test.cpp -o gge-test -L../build -lGGE -lcpptest Running this on Fedora 21 gdb, I get: $ /usr/bin/gdb -nx -readnow test-gge GNU gdb (GDB) Fedora 7.8.2-38.fc21 Copyright (C) 2014 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-redhat-linux-gnu". Type "show configuration" for configuration details. For bug reporting instructions, please see: <http://www.gnu.org/software/gdb/bugs/>. Find the GDB manual and other documentation resources online at: <http://www.gnu.org/software/gdb/documentation/>. For help, type "help". Type "apropos word" to search for commands related to "word"... Reading symbols from gge-test...expanding to full symbols...done. (gdb) start Temporary breakpoint 1 at 0x8049b6e: file test.cpp, line 173. Starting program: /home/keiths/gorgon-ge-code/Tests/gge-test Missing separate debuginfos, use: debuginfo-install glibc-2.20-8.fc21.i686 Temporary breakpoint 1, main (argc=1, argv=0xffffcd04) at test.cpp:173 173 Test::Suite ts; Missing separate debuginfos, use: debuginfo-install cpptest-1.1.2-3.fc21.i686 libgcc-4.9.2-6.fc21.i686 libstdc++-4.9.2-6.fc21.i686 (gdb) f #0 main (argc=1, argv=0xffffcd04) at test.cpp:173 173 Test::Suite ts; and I can "n" all the way through the program. My advice: *attach* your executable to this bug report and/or run gdb under gdb and provide a stack backtrace. -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2015-03-17 16:30 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 [this message] 2015-03-17 19:31 ` cemkalyoncu at gmail dot com 2015-03-17 20:46 ` cemkalyoncu at gmail dot com 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-wkUAqdo1m2@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).