| TIP: Click on subject to list as thread! | ANSI |
| echo: | |
|---|---|
| to: | |
| from: | |
| date: | |
| subject: | Kernel debugger fails to |
Denis,
Replying to a message of Denis Tonn to Erwin Hogeweg:
[...]
DT> Warp Connect is revision 8.209. The debug kernel for this level
DT> erroneously reports itself as 8.200. Make sure you have the correct
DT> retail kernel installed for Warp Connect, it should report 8.209 from
DT> the BLDLEVEL OS2KRNL command. Do NOT use the ver /r command to check
DT> the revision level (this is probably what is wrong),
Yes it was. Thank to Murray Lesser I already figured this out. It indeed
reports itself as 8.209.
DT> The debug kernel (and dump formatter and symbol files) for Warp
DT> Connect level are on the CDROM shipped with the product.
Aha, this I didn't know yet. Only, after reading the Debug Kernel Reference
manual, I am no longer sure that I really need/want this. All I want to do
is step through an suspicious API call ( PrfWriteProfileData() ). I guess
that all I have to do is tell my debugger (IPMD) to include the *.SYM
files. I just haven't figured out yet how to do this so if you can give me
hint...
Bye, Erwin Hogeweg
fidonet : 2:500/120.6046
OS2NET : 81:431/520.6046
e-mail : e.hogeweg{at}dosgg.nl
---
* Origin: Highway Express/2 (2:500/120.6046)SEEN-BY: 50/99 54/99 270/101 620/243 625/155 711/401 413 430 934 712/311 407 SEEN-BY: 712/505 506 517 623 624 704 713/317 800/1 @PATH: 500/120 7 9 3 396/1 270/101 712/624 711/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™.