Question about "kdb error: type" erro

[Carfield Yim]

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

[Ryan Hamilton]

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

> --
> You received this message because you are subscribed to the Google
> Groups "Kdb+ Personal Developers" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to personal-kdbpl...@googlegroups.com.
> To post to this group, send email to personal...@googlegroups.com.
> Visit this group at http://groups.google.com/group/personal-kdbplus?hl=en.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>


--
TimeStored.com - KDB+ Software, Training, Consulting

[Oleg Zakharov]

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

On Feb 13, 2013 8:18 PM, "Ryan Hamilton" <ry...@timestored.com> wrote:

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


On 2/13/2013 3:59 PM, Carfield Yim wrote:

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
--
You received this message because you are subscribed to the Google Groups "Kdb+ Personal Developers" group.

To unsubscribe from this group and stop receiving emails from it, send an email to personal-kdbplus+unsubscribe@googlegroups.com.
To post to this group, send email to personal-kdbplus@googlegroups.com.

Visit this group at http://groups.google.com/group/personal-kdbplus?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

--
TimeStored.com - KDB+ Software, Training, Consulting

--
You received this message because you are subscribed to the Google Groups "Kdb+ Personal Developers" group.

To unsubscribe from this group and stop receiving emails from it, send an email to personal-kdbplus+unsubscribe@googlegroups.com.
To post to this group, send email to personal-kdbplus@googlegroups.com.