[Gambas-user] Debugging Gambas (again)

Cedron Dawg cedron at exede.net
Sat Apr 27 14:59:46 CEST 2019

Hi K,

I appreciate that.

Had you said:  "Please note I don't think there is a problem with my code, I am looking for guidance on how to go about debugging Gambas."

Instead of:

"Please note I am not looking for anyone to tell me the problem with my code, I am looking for guidance on how to go about debugging a Gambas application."

Then I wouldn't have had to fluster Jussi a little bit.  (BTW, Jussi, I wrote a comprehensive byte-code interpreter in 8086 assembly in Real Mode as a DOS 3.1 TSR that was used in production for several years, circa 1988)

I don't like ncurses, it is a bloated mess, but it's been around a long time, so if that is the locus of the problem, I would suspect gb.ncurses first.

I've attached an incomplete project which you might find useful.  It is part of a path towards a lightweight ncurses "equivalent".  The attached code is essentially the same as early BASICs:  It gives you a Locate statement for printing and provides an Inkey and Line Input for reading terminal input with VT100 escape sequences translated to character codes.


----- Original Message -----
From: "KKing" <kicking177 at gmail.com>
To: "user" <user at lists.gambas-basic.org>
Sent: Saturday, April 27, 2019 4:41:36 AM
Subject: Re: [Gambas-user] Debugging Gambas (again)

thankyou, that gives me a better understanding and lets me plan next 
steps, which will be to grab latest sources and compile with the 
"-DDEBUG_ME" to CFLAGS and CXXFLAGS, which I will not have done last time.

@Ced: I am "interested in these advanced debugging techniques" and also 
because I've been through the
Traditional source code level debugging, e.g. print statements, 
breakpoints, and watch variables
And found that it fails in a section of code that is called repeatedly 
without issue until the segfault and by nature of the data that is being 
passed around and changing the order it is entered I know it is not the 
data and on face of it not program code. The goal is to not only get the 
code to run but also to establish why it is failing and if it is within 
Gambas internals or a component, to help identify and improve it, or in 
worst case have a "do not do this with Gambas".

-------------- next part --------------
A non-text attachment was scrubbed...
Name: NiceTerm-0.0.4.tar.gz
Type: application/x-compressed-tar
Size: 25261 bytes
Desc: not available
URL: <https://lists.gambas-basic.org/pipermail/user/attachments/20190427/a0ca0d23/attachment-0001.bin>

More information about the User mailing list