|
From: TheFGFSEagle <the...@gm...> - 2023-07-12 17:57:02
|
Wait. I thought you got the error from a console output like: 123.45 [ALERT]:nasal Nasal runtime error: string index 3 out of bounds (size: 3) If it is an ordinary C++ error, it could come from anywhere, not necessarily Nasal. Am Mi., 12. Juli 2023 um 04:34 Uhr schrieb Wayne Bragg <kil...@co... >: > Well that is a little help, so this is a nasal error. > > > > I’m not the one getting this particular error so I cannot trace. I finally > set up a way to do that in Windows with Visual Studios but I am not really > “fluid” with it. I used it maybe once. > > > > Wayne > > > > *From: *TheFGFSEagle <the...@gm...> > *Sent: *Monday, July 10, 2023 4:44 PM > *To: *FlightGear developers discussions > <fli...@li...> > *Subject: *Re: [Flightgear-devel] Question about a hard to trace error > > > > Isn't there no traceback ??? This can happen any place in Nasal where an > char at an index past the end of the string is requested. > > > > Am Mo., 10. Juli 2023 um 19:29 Uhr schrieb Wayne Bragg < > kil...@co...>: > > string index 3 out of bounds (size: 3) > > > > I’ve seen this error before and always associated it with bad data, > usually in a GUI menu. Can anyone shed some light on when you might > encounter this error. > > > > For example, > > Reading cached data and trying to populate a sting var with the wrong type > or size of data? > > A GUI menu opening and reading the wrong type of size of data for a menu > var or property? > > > > Any info on where in the core this error can be thrown would be helpful, > like can you get this from core code or only GUI related, nasal? > > > > Wayne > > > > > > _______________________________________________ > Flightgear-devel mailing list > Fli...@li... > https://lists.sourceforge.net/lists/listinfo/flightgear-devel > > > _______________________________________________ > Flightgear-devel mailing list > Fli...@li... > https://lists.sourceforge.net/lists/listinfo/flightgear-devel > |