[binutils-gdb] gdb, btrace: Throw an error for empty recordings when replaying starts.

Felix Willgerodt fwillger@sourceware.org
Tue May 17 10:43:53 GMT 2022


https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=49a73ab9d345e1cd412a93b34a0b8c166603d80e

commit 49a73ab9d345e1cd412a93b34a0b8c166603d80e
Author: Felix Willgerodt <felix.willgerodt@intel.com>
Date:   Mon May 9 10:12:39 2022 +0200

    gdb, btrace: Throw an error for empty recordings when replaying starts.
    
    This makes record_btrace_start_replaying() more consistent, as it already
    errors out e.g. on a recording with only gaps.

Diff:
---
 gdb/record-btrace.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/gdb/record-btrace.c b/gdb/record-btrace.c
index 373d82b8b99..3f8a69dd04f 100644
--- a/gdb/record-btrace.c
+++ b/gdb/record-btrace.c
@@ -2017,7 +2017,7 @@ record_btrace_start_replaying (struct thread_info *tp)
 
   /* We can't start replaying without trace.  */
   if (btinfo->functions.empty ())
-    return NULL;
+    error (_("No trace."));
 
   /* GDB stores the current frame_id when stepping in order to detects steps
      into subroutines.


More information about the Gdb-cvs mailing list