public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug symtab/26063] inconsistent behaviors at -O2 Date: Wed, 13 Jan 2021 15:18:09 +0000 [thread overview] Message-ID: <bug-26063-4717-vbPorIu6Ea@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-26063-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=26063 --- Comment #4 from Tom de Vries <vries at gcc dot gnu.org> --- Hmm, this could work, let's put it through some testing: ... diff --git a/gdb/infrun.c b/gdb/infrun.c index 940f575e22a..49fbad35296 100644 --- a/gdb/infrun.c +++ b/gdb/infrun.c @@ -7021,6 +7021,16 @@ process_event_stop_test (struct execution_control_state *ecs) infrun_debug_printf ("stepped to a different line, but " "it's not the start of a statement"); } + else + { + /* We are at the start of a different line, however, this line is + not marked as a statement, and we have changed frame. We + ignore this line table entry, and continue stepping forward, + looking for a better place to stop. + Because we have changed frame, set stop_pc_sal.line to 0, to let + set_step_info set ecs->event_thread->current_line to 0. */ + stop_pc_sal.line = 0; + } } /* We aren't done stepping. ... -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2021-01-13 15:18 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-05-30 2:51 [Bug symtab/26063] New: " yangyibiao at hust dot edu.cn 2020-05-30 2:52 ` [Bug symtab/26063] " yangyibiao at hust dot edu.cn 2021-01-13 8:38 ` yangyibiao at outlook dot com 2021-01-13 12:44 ` yangyibiao at outlook dot com 2021-01-13 12:58 ` yangyibiao at outlook dot com 2021-01-13 14:24 ` vries at gcc dot gnu.org 2021-01-13 15:18 ` vries at gcc dot gnu.org [this message] 2021-01-14 13:00 ` [Bug breakpoints/26063] " vries at gcc dot gnu.org 2021-01-14 13:28 ` vries at gcc dot gnu.org 2021-01-29 12:36 ` cvs-commit at gcc dot gnu.org 2021-01-29 12:37 ` vries at gcc dot gnu.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-26063-4717-vbPorIu6Ea@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).