Community
Participate
Working Groups
- connect to a remote Crossfire server - set a breakpoint, hit it - step into or over once -> the current line and variables update accordingly, but the into/over/out buttons at the top of the Debug view are left disabled, so a second step cannot be done
I dug into this one a bit and found that when connected to FF / FB after we send the continue request with into / next / out we get a success response immediately followed by an onResume event, which causes the debugger to resume (disabling the buttons because the debugger is resumed). I think the crossfire server should not be sending an onResume event in this case, since we get the success response from our request. I can't think of a case where the actual resume would be delayed (like the suspend request can be). I will open a bug against crossfire for more discussion about this.
Agreed, onResume should not happen in this case. The problem also happens with the IE server, and it's not sending this event, so there's a different cause in this case. FF/FB would probably also hit this if the inappropriate onResume event was not being sent.
I opened http://code.google.com/p/fbug/issues/detail?id=4288 to track what crossfire is doing while stepping.
Created attachment 193890 [details] fix I found a few issues that contributed to this problem: 1. the onResume / onBreak were not properly processed in the order crossfire sent them, which would get our model in a bad state 2. an onResume event had the bad habit of then sending a continue request from our client The patch maintains the proper ordering for received events and does not send a continue request following an onResume event
applied patch to HEAD
