public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "dje at google dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug breakpoints/15360] New: can't step into function
Date: Thu, 11 Apr 2013 23:49:00 -0000	[thread overview]
Message-ID: <bug-15360-4717@http.sourceware.org/bugzilla/> (raw)

http://sourceware.org/bugzilla/show_bug.cgi?id=15360

             Bug #: 15360
           Summary: can't step into function
           Product: gdb
           Version: HEAD
            Status: NEW
          Severity: normal
          Priority: P2
         Component: breakpoints
        AssignedTo: unassigned@sourceware.org
        ReportedBy: dje@google.com
    Classification: Unclassified


Compiling this with -g, stepping into "function" doesn't work.

(gdb) start
Temporary breakpoint 1 at 0x400508: file foo.c, line 23.
Starting program: /home/dje/src/play/a.out

Temporary breakpoint 1, main (argc=1, argv=0x7fffffffe848) at foo.c:23
23        function();
(gdb) s
[Inferior 1 (process 19896) exited normally]
(gdb) 

struct foo
{
  int i;
  ~foo(){return;};
};


int function()
{
  do{
    int i = 0;
    int j = i + 4;
    foo bar;
    if(0)
      {
        continue;
      }
    return 1;
  }while(1);
}
int main (int argc, char* argv[])
{
  function();
  return 0;
}

-- 
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.


             reply	other threads:[~2013-04-11 23:49 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-11 23:49 dje at google dot com [this message]
2013-04-11 23:56 ` [Bug breakpoints/15360] " dje at google dot com
2013-04-12  8:52 ` palves at redhat dot com
2013-04-12 17:59 ` tromey at redhat dot com
2013-04-12 18:16 ` palves at redhat dot com
2013-04-12 18:26 ` palves at redhat dot com
2024-01-08 16:49 ` ssbssa at sourceware dot org

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-15360-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: 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).