public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "palves at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug breakpoints/16280] Step into an inline function with varargs doesn't stop
Date: Sun, 01 Dec 2013 22:08:00 -0000	[thread overview]
Message-ID: <bug-16280-4717-FfhVeEdORu@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-16280-4717@http.sourceware.org/bugzilla/>

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

--- Comment #3 from Pedro Alves <palves at redhat dot com> ---
So, a simpler reproducer is to try to set a breakpoint in the function, and run
to it, no stepping involved, which fails as well:

...
Temporary breakpoint 4, main (argc=1, argv=0x7fffffffdb38) at main.cpp:6
6           step.show("hi %s\n", "there");
(gdb) b Step::show
Breakpoint 2 at 0x400712: file Step.h, line 15.
(gdb) c
Continuing.
infrun: clear_proceed_status_thread (process 20347)
infrun: proceed (addr=0xffffffffffffffff, signal=GDB_SIGNAL_DEFAULT, step=0)
infrun: resume (step=0, signal=GDB_SIGNAL_0), trap_expected=0, current thread
[process 20347] at 0x4006bb
hi there
infrun: wait_for_inferior ()
infrun: target_wait (-1, status) =
infrun:   20347 [process 20347],
infrun:   status->kind = exited, status = 0
infrun: infwait_normal_state
infrun: TARGET_WAITKIND_EXITED
[Inferior 1 (process 20347) exited normally]
infrun: stop_stepping
(gdb)

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


  parent reply	other threads:[~2013-12-01 22:08 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-01 19:40 [Bug breakpoints/16280] New: " psmith at gnu dot org
2013-12-01 22:03 ` [Bug breakpoints/16280] " palves at redhat dot com
2013-12-01 22:05 ` palves at redhat dot com
2013-12-01 22:08 ` palves at redhat dot com
2013-12-01 22:08 ` palves at redhat dot com [this message]
2013-12-01 22:11 ` palves at redhat dot com
2013-12-01 22:23 ` palves at redhat dot com
2013-12-01 22:30 ` palves at redhat dot com
2013-12-01 22:40 ` palves at redhat dot com
2013-12-02  0:14 ` psmith at gnu dot org
2013-12-17 10:47 ` 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-16280-4717-FfhVeEdORu@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).