public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "vsoftco at gmail dot com" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug breakpoints/16880] New: GDB does not step into template functions OS X Mavericks Date: Mon, 28 Apr 2014 23:32:00 -0000 [thread overview] Message-ID: <bug-16880-4717@http.sourceware.org/bugzilla/> (raw) https://sourceware.org/bugzilla/show_bug.cgi?id=16880 Bug ID: 16880 Summary: GDB does not step into template functions OS X Mavericks Product: gdb Version: 7.7 Status: NEW Severity: normal Priority: P2 Component: breakpoints Assignee: unassigned at sourceware dot org Reporter: vsoftco at gmail dot com Hi, I am using gdb on OS X Mavericks, and whenever I try to step in a template function, gdb steps over (same when I set a breakpoint inside a template function, it is never reached, as if the breakpoint does not exist). This happens for even the simplest template functions defined inside of main.cpp. My target OS is OS X Mavericks, I used both gdb 7.6 and gdb 7.7, same behaviour. I tried it on more than one machine that runs Mavericks. I also tried using various versions of g++ (4.7, 4.8, 4.9) to compile my program. I also tried to use -fno-inline option when compiling, still same thing... Under any other OS (Linux/Windows/Solaris), gdb steps in template functions. It seems to be a problem related to OS X Mavericks. Thanks! -- You are receiving this mail because: You are on the CC list for the bug.
next reply other threads:[~2014-04-28 23:32 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-04-28 23:32 vsoftco at gmail dot com [this message] 2014-04-28 23:39 ` [Bug breakpoints/16880] " vsoftco at gmail dot com 2014-04-28 23:41 ` vsoftco at gmail dot com 2014-04-28 23:42 ` vsoftco at gmail dot com 2014-05-03 21:55 ` vsoftco 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-16880-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).