Bug 409793 - Reverse Debugging reaching exit becomes not responsive
Summary: Reverse Debugging reaching exit becomes not responsive
Status: NEW
Alias: None
Product: CDT
Classification: Tools
Component: cdt-debug-dsf-gdb (show other bugs)
Version: 8.2   Edit
Hardware: PC Linux
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact: Jonah Graham CLA
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-06-03 19:13 EDT by Alvaro Sanchez-Leon CLA
Modified: 2020-09-04 15:17 EDT (History)
3 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Alvaro Sanchez-Leon CLA 2013-06-03 19:13:23 EDT
When a reverse debugging is on and the execution reaches the exit, the session becomes unresponsive to any reverse commands, 
the gdb console displays the text below, ideally reverse debugging should still be available. 
  
_____
Do you want to auto delete previous execution log entries when record/replay buffer becomes full (record full stop-at-limit)?([y] or n) [answered Y; input not from terminal]
The next instruction is syscall exit_group.  It will make the program exit.  Do you want to stop the program?([y] or n) [answered Y; input not from terminal]
Process record: inferior program stopped.