[Gambas-user] Debugging Gambas (again)

Jussi Lahtinen jussi.lahtinen at gmail.com
Sat Apr 27 02:31:59 CEST 2019

Understanding why sig11 is bug in Gambas requires some understanding of how
modern operating systems and how interpreted languages like Gambas work.

Only way this could not be bug in Gambas (it may very well be *also* bug in
the OPs code), is that the OP is calling external function written in some
other language and the error comes from there, but by quick look it doesn't
look like that.


On Sat, Apr 27, 2019 at 2:27 AM Cedron Dawg <cedron at exede.net> wrote:

> 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
> ----[ Gambas mailing-list is hosted by https://www.hostsharing.net ]----
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.gambas-basic.org/pipermail/user/attachments/20190427/0047e016/attachment.html>

More information about the User mailing list