public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "trass3r at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug record/29260] Stopped event should contain reason for 'No more reverse-execution history'
Date: Fri, 17 Jun 2022 20:58:57 +0000	[thread overview]
Message-ID: <bug-29260-4717-91D33dDG9V@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-29260-4717@http.sourceware.org/bugzilla/>

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

--- Comment #1 from trass3r <trass3r at gmail dot com> ---
Code of interest:

handle_inferior_event(infrun.c:5858):

    case TARGET_WAITKIND_NO_HISTORY:
      /* Reverse execution: target ran out of history info.  */

      /* Switch to the stopped thread.  */
      context_switch (ecs);
      infrun_debug_printf ("stopped");

      delete_just_stopped_threads_single_step_breakpoints ();
      ecs->event_thread->set_stop_pc
        (regcache_read_pc (get_thread_regcache (inferior_thread ())));

      if (handle_stop_requested (ecs))
        return;

      gdb::observers::no_history.notify (); // just prints the line in
print_no_history_reason
      stop_waiting (ecs);

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

  reply	other threads:[~2022-06-17 20:58 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-17 17:35 [Bug record/29260] New: " trass3r at gmail dot com
2022-06-17 20:58 ` trass3r at gmail dot com [this message]
2022-06-18 16:20 ` [Bug record/29260] " tromey at sourceware dot org
2022-06-18 17:08 ` trass3r at gmail dot com
2022-06-18 17:09 ` trass3r at gmail dot com
2023-01-18 13:49 ` blarsen 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-29260-4717-91D33dDG9V@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).