Question about "kdb error: type" erro

Community Support
1

Hi all

I just inherits a Q module and found out from the log that there are some println of “kdb error: type”. It is not always happened and there should not be mismatched assignment after checking. Other than adding a lot of print line, is there anyway to check where the problem is? If there any program like lint help to check the code?

Regards

2

X-Gm-Message-State: ALoCoQmsQdWygnljHfm31me+abKEc3evz2VrQPFyEQi0fSUczRlAy7iWu08T6hPla/wIkA4p9Rpw

Hi Carfield,

Error information, brief as it is is given here:
http://code.kx.com/wiki/Errors

However the logged error you gave is probably being protectively
evaluated as 'type is a thrown error. If you can remove it from the
protected evaluation it may stop in the middle of the stack where the
problem occurs… You’ll see the q prompt change to:
q))

If your new to kdb:

Protected evaluation is like try/catch from C++ etc, details here:
http://code.kx.com/wiki/JB:QforMortals/execution\_control#Protected\_Evaluation

Some help debugging in kdb can be found at:
http://www.timestored.com/kdbGuides/debuggingKdb

There’s definitely no static analysis tools for kdb,
Good luck,

Ryan Hamilton

3

Also, you can try out statefull injectable debugger in the latest version of qpad (qinsightpad.com) to view execution and call stack, variables and probably the cause of what’s going on at the time of signal being thrown remotely.

Comes quite handy at times ;)

Cheers,
Oleg