Bugs: Browse | Submit New | Admin

[#210] debugger: not sure if this is a bug or just an "unexpected" behaviour

Date:
2003-12-24 09:49
Priority:
3
Submitted By:
Laurent Julliard (ljulliar)
Assigned To:
Laurent Julliard (ljulliar)
Category:
Debugger
State:
Open
Summary:
debugger: not sure if this is a bug or just an "unexpected" behaviour

Detailed description
actually as far as i'm concerned it's at least a buglet but others might think differently.

when using the debugger eval works as expected i.e. '1 + 1' gives 2 until i run the debugger on a program and then evalgives
the following error "can't eval - process stopped"

i assume that druby is no longer running which is why it doesn't do anything but it is semi-annoying

 (was Savannah bug #3263)

Add A Comment: Notepad

Please login


Followup

Message
Date: 2003-12-24 09:51
Sender: Laurent Julliard

Logged In: YES 
user_id=539

(From ukscone)
I honestly don't know what the ideal solution would be. obviously
it would be far better to be evaluating within the druby context
but that is gone so it isn't possible. however even just having
an eval in the freeride context would be handy if only to use
it as a simple calculator or to run ri (that'd work woudn't it?)
-- anyway i'll leave it up to my betters to decide the hows,
whys and wherefores
Date: 2003-12-24 09:50
Sender: Laurent Julliard

Logged In: YES 
user_id=539

I agree with you that it is semi-annoying and I wondered for
some time what to do myself. The reason why we can't eval as
you said is because the remote debugger is finished. So an eval
would have to be done in the context of the freeride process
itself. The problem is that it could be very misleading to user
who think that they are still evaluating in the context of the
debugged process.

What do you think? 

Attached Files:

Name Description Download
No Files Currently Attached

Changes:

Field Old Value Date By
summarydebugger: not sure if this is a bug or just an "unexpected" behaviour2003-12-24 09:51ljulliar
summarydebugger: not sure if this is a bug or just an "unexpected" behaviour2003-12-24 09:50ljulliar