Liberty BASIC Community Forum
« LB debugger »

Welcome Guest. Please Login or Register.
Apr 28th, 2017, 4:48pm


Rules|Home|Help|Search|Recent Posts|Notification


« Previous Topic | Next Topic »
Pages: 1  Notify Send Topic Print
 thread  Author  Topic: LB debugger  (Read 222 times)
petermat
New Member
Image


member is offline

Avatar




PM


Posts: 38
xx LB debugger
« Thread started on: Apr 19th, 2017, 2:55pm »

I have two problems with the LB debugger - and I am hoping they are just my ignorance and I will be put straight.
1. Debugger does not display globals whilst stepping through a function or subroutine. Consequently my code is littered with statements copying globals to locals so I can see the value while debugging.
2. (lesser issue) The placement of the variable display window and code window is fixed. With today's 16*9 displays, side by side would be much more useful.

?

PS Actually I have a much longer wish list for the debugger - but fixing these two would speed up my daily work the most.
User IP Logged

CarlGundel
Administrator
ImageImageImageImageImage


member is offline

Avatar

author of Liberty BASIC


Homepage PM


Posts: 2749
xx Re: LB debugger
« Reply #1 on: Apr 21st, 2017, 08:18am »

Maybe I can squeeze some small changes into the debugger for v4.5.1. Post your wish list and I'll try to manage something. Maybe a screen mockup would be useful too?

-Carl
User IP Logged

author of Liberty BASIC
http://www.libertybasic.com
Rod
Global Moderator
ImageImageImageImageImage


member is offline

Avatar

Graphics = goosebumps!


PM

Gender: Male
Posts: 5251
xx Re: LB debugger
« Reply #2 on: Apr 21st, 2017, 08:35am »

Another tickbox [] Show global variables would allow you to quickly check global values and then hide them, same as for default variables.
User IP Logged

petermat
New Member
Image


member is offline

Avatar




PM


Posts: 38
xx Re: LB debugger
« Reply #3 on: Apr 26th, 2017, 12:55pm »

on Apr 21st, 2017, 08:18am, CarlGundel wrote:
Maybe I can squeeze some small changes into the debugger for v4.5.1. Post your wish list and I'll try to manage something. Maybe a screen mockup would be useful too?

-Carl


Thanks for this - suggestions are, in rough order of personal importance:

* Globals should be selectively (individually, best, 'all' second best) visible in IDE debugger - and printable via the IDE 'execute' function.
* The variable and code display windows should be separable so they can each be placed where they fit best on the user screen(s)
* User should be able to put a 'watch' on specific variables, so that when the selected variable attains a specific value whilst free running, execution halts at that point - just like it hit a breakpoint.
* User should be able to move the run point backwards to redo code or forward to skip code
* Add line numbers to give better integration with LB workshop and Notepad++
* Allow cut / paste into / from the execute box
* Enable following a function call down if embedded in an IF statement
* Data shown in the ide should change on using "execute" without having to execute the next 'real' instruction

(Whew!)

Peter

I will do a screen mockup if you feel it will help - but not sure how many of the above to include?

PS - I have not done any Smalltalk for years, but would be willing to have a go if it would help - though I suspect it would be more trouble to explain than to do!


« Last Edit: Apr 26th, 2017, 2:50pm by petermat » User IP Logged

Brandon Parker
Board Moderator

member is offline

Avatar




PM

Gender: Male
Posts: 1074
xx Re: LB debugger
« Reply #4 on: Apr 26th, 2017, 5:19pm »

Here's a wish from me.....

Allow the debugger to step past an error that way if the error is within a sub/ function and handled correctly the progression of the program can continue.

{:0)

Brandon
User IP Logged

Windows 7 Home Premium 64-bit Intel(R) Quad Core(TM) i5 CPU M 430 @ 2.27GHz 4GB DDR3 RAM
petermat
New Member
Image


member is offline

Avatar




PM


Posts: 38
xx Re: LB debugger
« Reply #5 on: Apr 26th, 2017, 7:05pm »

Brandon,
I agree, but that problem is largely covered by my fourth bullet - "User should be able to move the run point . . . forward to skip code" - thereby avoiding the error. Any needed data changes could be handled by the existing 'execute' - aided by coping and pasting some code. (Provided that 'execute' can access globals!)

Still, your suggestion is a neater way of coping with that particular problem.

Peter.
« Last Edit: Apr 26th, 2017, 7:05pm by petermat » User IP Logged

cundo
Guru
ImageImageImageImageImage


member is offline

Avatar




PM

Gender: Male
Posts: 609
xx Re: LB debugger
« Reply #6 on: Apr 26th, 2017, 8:01pm »

Quote:
Globals should be selectively (individually, best, 'all' second best) visible in IDE debugger - and printable via the IDE 'execute' function.
I don't understand this. How is that "second best", and the others, best, all?
Thanks.
User IP Logged

cundo
petermat
New Member
Image


member is offline

Avatar




PM


Posts: 38
xx Re: LB debugger
« Reply #7 on: Apr 26th, 2017, 9:49pm »

Sorry - too much brevity and not enough clarity. What I meant was that in my ideal world, I could:
1. Have the option to "select all globals" which would then dynamically show the current values of all globals in the data window. (With a corresponding deselect.)
2. Or, pull up a list of all globals listed alphabetically and then be able to select any number of globals individually. Thereafter only the selected globals' values would be shown dynamically in the data window - until the selection was changed or the option switched off.

Having both these options would be my best solution, only having option 1 would be my second best. This is because with a sizeable program the number of globals could take up a lot of screen space. Of course having the data window separate from the code window and independently sizeable would help - multiple columns in this window would help even more.
« Last Edit: Apr 26th, 2017, 9:51pm by petermat » User IP Logged

Brandon Parker
Board Moderator

member is offline

Avatar




PM

Gender: Male
Posts: 1074
xx Re: LB debugger
« Reply #8 on: Today at 4:00pm »

on Apr 26th, 2017, 7:05pm, petermat wrote:
Brandon,
I agree, but that problem is largely covered by my fourth bullet - "User should be able to move the run point . . . forward to skip code" - thereby avoiding the error. Any needed data changes could be handled by the existing 'execute' - aided by coping and pasting some code. (Provided that 'execute' can access globals!)

Still, your suggestion is a neater way of coping with that particular problem.

Peter.


Peter,
I think you misunderstand; I mean to allow the error to occur, trap it, and keep moving automatically just as the runtime engine does. I would not be stepping through the code; the library (my Dynamic Array Library) works on this specific ability, but it makes it impossible to use the debugger.


{:0)

Brandon
User IP Logged

Windows 7 Home Premium 64-bit Intel(R) Quad Core(TM) i5 CPU M 430 @ 2.27GHz 4GB DDR3 RAM
Pages: 1  Notify Send Topic Print
« Previous Topic | Next Topic »

Rules|Home|Help|Search|Recent Posts|Notification

Donate $6.99 for 50,000 Ad-Free Pageviews!

| |

This forum powered for FREE by Conforums ©
Sign up for your own Free Message Board today!
Terms of Service | Privacy Policy | Conforums Support | Parental Controls