I've a DDT app that is generating a "stack fault in KERNEL32.DLL at address
016F:BFF73625" when run on Win98. The base address for KERNEL32 is BFF70000
but the MS DEPENDS tool doesn't show any function near the address of the
stack fault; the closest one is "FT_EXIT32" at BFF72C89.
I've traced it down to the DIALOG SHOW MODELESS statement, but beyond that
I'm a bit stuck. The window partially paints, showing listboxes and textboxes,
but no labels or buttons.
The app works fine on my dev PC (Win2K Pro).
To add to the confusion, I have another DDT app that works fine on 98. The failing
app does use a few external DLLs, but they aren't called upon until the user
clicks the "Go" button.
Does the DIALOG SHOW statement trigger something that would cause Windows to walk
the DLL dependencies, and finding a problem in an external DLL cause the stack fault?
Thanks!
------------------
Mark Newman
[This message has been edited by Mark Newman (edited March 01, 2001).]
016F:BFF73625" when run on Win98. The base address for KERNEL32 is BFF70000
but the MS DEPENDS tool doesn't show any function near the address of the
stack fault; the closest one is "FT_EXIT32" at BFF72C89.
I've traced it down to the DIALOG SHOW MODELESS statement, but beyond that
I'm a bit stuck. The window partially paints, showing listboxes and textboxes,
but no labels or buttons.
The app works fine on my dev PC (Win2K Pro).
To add to the confusion, I have another DDT app that works fine on 98. The failing
app does use a few external DLLs, but they aren't called upon until the user
clicks the "Go" button.
Does the DIALOG SHOW statement trigger something that would cause Windows to walk
the DLL dependencies, and finding a problem in an external DLL cause the stack fault?
Thanks!
------------------
Mark Newman
[This message has been edited by Mark Newman (edited March 01, 2001).]
Comment