On 13 December 2012 10:30, Stéphane Ducasse <stephane.ducasse@inria.fr> wrote:
Now adrian I imagine that you saw that people worked on this bug and this is a rather complex one. So I would suggest to you to avoid to draw conclusions too fast.
yes, if i remember, we tried to approach it at least once.. but unfortunately it requires a lot deeper knowledge about bytecode and (de)optimizations to fix highlight.
Stef
On Dec 12, 2012, at 11:28 PM, adrians wrote:
Well, it just seems that I'm whining here instead of contributing, but if the debugger is indeed a very (if not the most) useful tool which is used in pretty much every bit of fix-up work, fixing it if it is broken would have to come before all else, no? Otherwise, any work that needs to be done until it is looked at is just compounded.
Maybe it would make sense to correct (in the current code) to a small degree just one of the things that is currently broken. No frills, but just getting a more accurate indication of where the PC is - at least have it on the correct line of code if it can't be pinpointed more accurately without too much hassle. I'm curious what derails the location highlighting as half of the time it is close, if not correct. Is it blocks that give it a hard time? It wouldn't be too bad if other things were going to take a while if you could at least keep track of where you were.
If the idea is to wait until a whole big refactoring can be done on this, I fear a fully debugger might be another year away.
-- Adrian
-- View this message in context: http://forum.world.st/Helping-the-noobs-help-out-i-e-fixing-the-debugger-tp4... Sent from the Pharo Smalltalk mailing list archive at Nabble.com.
-- Best regards, Igor Stasenko.