[Gambas-user] Debugging Gambas (again)

[Cedron Dawg]

Ideally that is true.  You shouldn't be able to throw anything at the underlying code and have it seg fault.  Nor am I ruling out some sort of Gambas bug in this situation.  But what is the difference between a seg fault and some other sort of cleaner error exit in this case?  (Assuming the OP's source code is flawed)

The fact that it happens as "after a certain number of entries the program fails" indicates either a capacity issue or a bad case scenario.  If it failed the first time, then go looking for an obvious Gambas bug.

My bet is that the problem ends up being in the OP's code, and maybe he's found a place where Gambas needs to be better fool-proofed.  However, adding parameter validation testing to every function call is a questionable endeavor.

Just 2 cents.  I am curious about how this turns out.


----- Original Message -----
From: "Jussi Lahtinen" <jussi.lahtinen at gmail.com>
To: "user" <user at lists.gambas-basic.org>
Sent: Friday, April 26, 2019 6:46:13 PM
Subject: Re: [Gambas-user] Debugging Gambas (again)

It is Gambas problem when there is segmentation fault from native Gambas code. 


Jussi