[Gambas-devel] gb3 stack backtrace and Unknown symbol

Kadaitcha Man nospam.nospam.nospam at ...176...
Sat Jan 9 08:26:12 CET 2010


Instructions for replicating what I describe here are contained in
Module2.module of the attached code. When you follow those
instructions you will find additional steps documented in
Module1.module.

When debugging code execution across multiple modules it is not
possible to inspect the values of variables in a routine of another
module if you select the module by clicking on the module's tab in the
IDE. Gambas issues an "Unknown symbol" message when you try to insect
a variable, even if the routine in the module is an active part of the
current trace.

The only way to get at the variables in another module is to
double-click on the relevant method or routine in the stack backtrace
window, even if the module window is already open in another tab. When
you double-click on the relevant method or routine in the stack
backtrace window, you can't go back to the previous module by clicking
on the module's tab in the IDE and still see the variables for that
module because gb3 now issues "Unknown symbol" messages for that
module instead. Again, you must double-click the previous
module.methodname in the stack backtrace window, despite the module's
code window already being open in another tab.

Is this behaviour by design?
-------------- next part --------------
A non-text attachment was scrubbed...
Name: UnknownSymbol.tar.gz
Type: application/x-gzip
Size: 9087 bytes
Desc: not available
URL: <http://lists.gambas-basic.org/pipermail/devel/attachments/20100109/a769b194/attachment.bin>


More information about the Devel mailing list