| TIP: Click on subject to list as thread! | ANSI |
| echo: | |
|---|---|
| to: | |
| from: | |
| date: | |
| subject: | Re: OS/2 programming tips ??? |
Hello Mike, 24.04.95 23:45, you wrote a message to David Etheredge: [...much interesting stuff deleted...] MB> If what you want is the ability to debug using dumps, then you MB> should look at the native OS/2 system trace facility. This MB> allows you to define logging events and checkpoints in your MB> code that are recorded in a large ring buffer by the MB> operating system. In the event of a crash, the trace buffer MB> can be written out to disk. Do you know anything additional about this feature? I used it (DevHelp_SysTrace) in a debugging version of our ADD. It would be nice to keep it in the retail version but I decided against it because I don't know which 'major trace event code' I should use. Is there a predefined value for ADD's or is this number provided by IBM on a per vendor basis? Bye, Vitus --- Sqed/32 0.999/r00228* Origin: Really a Point of BetaBox, Walheim (2:2474/100.20) SEEN-BY: 105/42 620/243 711/401 409 410 413 430 807 808 809 934 955 712/407 SEEN-BY: 712/515 628 704 713/888 800/1 7877/2809 @PATH: 2474/100 0 2476/2 2452/110 105/42 712/515 711/808 809 934 |
|
| SOURCE: echomail via fidonet.ozzmosis.com | |
Email questions or comments to sysop@ipingthereforeiam.com
All parts of this website painstakingly hand-crafted in the U.S.A.!
IPTIA BBS/MUD/Terminal/Game Server List, © 2025 IPTIA Consulting™.