Options
TKNs, Debug Info, and Modules
nicholasjames
Posts: 154
I'm curious if anyone knows more about the mystery of the NetLinx debugger and debugging included modules.
I know the debugging info is held in the master TKN (doubling your compiled file's size is easy to notice) but I'm not sure how that works with modules. It doesn't seem to matter whether or not you compiled with debug info for the module since nothing in the TKOs change except their date & time stamp. The total size of the master TKN isn't affected either, so obviously the compiler doesn't consult the module's TKN for debug info.
Obviously it requires the source for the module to be part of the workspace when I start debugging, but there's clearly more to it since, without any clear rhyme or reason, sometimes the debugger will jump into the module source, sometimes not. I thought perhaps that meant the TKN for the module also needed to be part of the workspace, but I'm hoping one of you would have some good info before I start the myriad of trial and error.
I know the debugging info is held in the master TKN (doubling your compiled file's size is easy to notice) but I'm not sure how that works with modules. It doesn't seem to matter whether or not you compiled with debug info for the module since nothing in the TKOs change except their date & time stamp. The total size of the master TKN isn't affected either, so obviously the compiler doesn't consult the module's TKN for debug info.
Obviously it requires the source for the module to be part of the workspace when I start debugging, but there's clearly more to it since, without any clear rhyme or reason, sometimes the debugger will jump into the module source, sometimes not. I thought perhaps that meant the TKN for the module also needed to be part of the workspace, but I'm hoping one of you would have some good info before I start the myriad of trial and error.
0