From: Andreas Schwab <schwab@suse.de>
To: Nancy <nancydreaming@gmail.com>
Cc: gdb@sourceware.org
Subject: Re: Is that a GDB bug?
Date: Mon, 12 Oct 2015 13:32:00 -0000 [thread overview]
Message-ID: <mvm8u78yzz4.fsf@hawking.suse.de> (raw)
In-Reply-To: <20151012132040.GA28674@vapier.lan> (Mike Frysinger's message of "Mon, 12 Oct 2015 09:20:40 -0400")
Mike Frysinger <vapier@gentoo.org> writes:
> next operates on statements, not lines.
That's not true.
(gdb) help step
Step program until it reaches a different source line.
Andreas.
--
Andreas Schwab, SUSE Labs, schwab@suse.de
GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7
"And now for something completely different."
next prev parent reply other threads:[~2015-10-12 13:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-12 12:46 Nancy
2015-10-12 13:20 ` Mike Frysinger
2015-10-12 13:32 ` Andreas Schwab [this message]
2015-10-12 16:39 ` Mike Frysinger
2015-10-12 16:56 ` Simon Marchi
2015-10-12 16:59 ` Andreas Schwab
2015-10-12 14:14 ` Pedro Alves
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=mvm8u78yzz4.fsf@hawking.suse.de \
--to=schwab@suse.de \
--cc=gdb@sourceware.org \
--cc=nancydreaming@gmail.com \
/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