28msec team mailing list archive

[David Graf <davidagraf@xxxxxxxxx>]

Hey Markus

I played a little bit with the debugger today. Uunfortunately, I still
found some stuff to improve:

1) You cannot assume that every unix installation has ledit installed
per default. E.g. it is not installed on mac os x.

2) After a print, '(xqdb)' is printed before the result of the print. Instead afterwards. E.g.:
(xqdb) p $entries
(xqdb) 
Query Evaluated: 
Value: <entry author="david" date="2010-03-07+01:00" time="21:48:17.601+01:00">Add your text here!</entry> Type:anyType

3)
Do you really wanna print 11 lines of code after each step? Can't you print just one line? The current line? If the user wants to see several lines around the current one, he can use the list command. Like in gdb.

4)
'(xqdb)' twice after an error message:
(xqdb) b guestbook 25
Couldn't find an expression to break in guestbook at line 25
(xqdb) (xqdb)

-- 
Debugger Beautification
https://bugs.launchpad.net/bugs/530225
You received this bug notification because you are a member of 28msec,
which is a direct subscriber.

Status in Sausalito Application Server: New

Bug description:
I tested the cmd debugger a little bit on mac. I found some things which should be enhanced:

1)
After start, it prints debugger.exe started. Should we change it so something like 'Sausalito CoreSDK Debugger started'?

2)
When the debugger suspends somewhere, it only prints the file and line number at that location. Also after a step. I think we should also print the source code line. And maybe remove the file and line number after a step. Like in gdb.

3)
When list is executed, it prints the source code without line numbers. I think the line numbers are necessary. Otherwise, it is hard to navigate.

4)
The '(xqdb)' printing seems to be broken. Sometimes it is printed twice, sometimes when the executed is not suspended, ...
'(xqdb)' should only be printed when the user is suposed to give a command.

5)
Can we also do the repeat trick from gdb? When a user presses enter without writing any command, it executes the preceding command again.

Can we do theses changes till the release?