in the good old days, there was a program alled SYAR.EXE that could read such infos.
It is not self explanatory and you have to understand the meaning of the signals.
The problem is that for each BC release, you need a signal names database to run this SW.
At the moment, I should say that when I need to nalyze a SYAR Dump, I escalade a metrix ticket to E/// and let them interpret this stuff.
The today's program is called WinSDE. Each BC version has it's own symbolic name database, but you can run the program also without those names, depends what you want to see in the interpreted SYAR dump.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.