Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Re: wowcamldebug exit issue #8479

Closed
vicuna opened this issue Feb 7, 2004 · 1 comment
Closed

Re: wowcamldebug exit issue #8479

vicuna opened this issue Feb 7, 2004 · 1 comment

Comments

@vicuna
Copy link

vicuna commented Feb 7, 2004

Original bug ID: 2187
Reporter: administrator
Assigned to: @xclerc
Status: resolved (set by @damiendoligez on 2015-03-13T19:31:40Z)
Resolution: suspended
Priority: high
Severity: minor
Target version: 4.03.0+dev / +beta1
Fixed in version: 4.03.0+dev / +beta1
Category: ~DO NOT USE (was: OCaml general)
Tags: patch

Bug description

On Sat, Feb 07, 2004 at 09:46:25AM +0100, Stefano Zacchiroli wrote:

On Fri, Feb 06, 2004 at 11:30:47AM -0800, Issac Trotts wrote:

Thanks for making wowcamldebug available. I wonder if you know how to
get around this problem:

Unfortunately no. I'm aware of the problem but last time I tried to
track it down it seemed to me that it was not deterministic. Are you
experiencing a reproducible behaviour?

Yes I think so.

I believe the problem is actually with ocamldebug. The error message

Lost connection with process -1 (active process)
between time 0 and time 10000

comes from the function Time_travel.forget_process. Here's my fix,
though I don't understand ocamldebug well enough to be sure that it's
really correct:

(* in debugger/main.ml *)

let rec protect ppf loop =
try
loop ppf
with
| End_of_file ->
(* This is hosed.
protect ppf (function ppf ->
forget_process
!current_checkpoint.c_fd
!current_checkpoint.c_pid;
pp_print_flush ppf ();
stop_user_input ();
loop ppf)
)
exit 0 (
This is basically what I want it to do. *)

Otherwise it just loops forever and you can't control-C or control-Z to
make it stop.

Cheers,
Issac

--
Issac Trotts
http://redwood.ucdavis.edu/~issac

@vicuna
Copy link
Author

vicuna commented Mar 13, 2015

Comment author: @damiendoligez

It's hard to tell exactly now that we've lost the context and we don't have a repro case, but there is a bug in forget_process when it gets called with pid=-1. I've fixed it in trunk (commit 15936).

@vicuna vicuna closed this as completed Mar 13, 2015
@vicuna vicuna added this to the 4.03.0 milestone Mar 14, 2019
@vicuna vicuna added the bug label Mar 19, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant