Re: debugger query: move execution point?

[vnpandey]

Thanks for your replies. Well My querry was posted based on experieance I had when trying to use debugger on my code.

The pain was that I have a lot of inputs to be given interactively (not via the command line) and once I have to restart the debugger, I have to enter all the inputs again even to the point till where things were fine. I may not be able to direct them via file simply because then trouble will arise when you want to give further inputs (after the place where things were fine) interactively which depend upon the results at different stages of the program.

The actual code (6000 lines) I am writing is to automate the processing of astronomical data from the Mauritius Radio Telescope to image the southern universe at radio wavelength (150MHz). The code basically calls a lot of programs and runs them with appropriate flags (this used to take earlier few months and now will be few hours).

So this feature may be of immense use in such cases. As pointed out that it will make the whole stuff very slow.

In principle if such a feature were existing, Is it possible to make it optional while invoking the debugger so as it does not make the code slow on programs when this feature is not needed ????.

Thanks once again for all your prompt answers. From your prompt answers it gives me a feeling as if I am talking to all you helpful monks. Hope I do take out sometime later when I am capable enough to write atleast something small for perl as my expression of thanks.
Pandey

[bean]

All these interactive inputs are going into variables, right? Dump the info you get via the inputs into files (you can do this directly to the variables using Data::Dumper or that other module I can't remember right now) and then, with a little hacking, you can run it without the inputs - just simulate the inputs with the information you got from them.

[vnpandey]

Yes! This is nice worth trying idea..

Well I wanted to do something like that, in a more rusty way although. For my application, perhabs this may be a little tedious, as my whole code is itself about flags and input output options which are too many and to be debugged itself.. so simulating the further inputs using the earlier inputs may be like writing a minicode itself..!

Let me see if I can do that with ease !
Thanks for your help!

Pandey