Stack Dump- NT DAO prog crashes on W95
David Ohlssen -- DAVIDO@COMMERCE.CTECH.AC.ZA
Tuesday, February 06, 1996
> >It's impossible to answre this question without a stack trace and
> >more information about the invalid memory access.
> >.B ekiM
Hows this:
It happens when I press the button to open the DAO recordset using
.Open() without parameters. The open has a try{}catch{} around it.
If I remember, the message was different when I did not have the
try/catch. Compiled on NT, trying to run on W95. All OK on NT.
TES953
caused an invalid page fault in module TES953.EXE at 0137:004015d7.
Registers:
EAX=00000000 CS=0137 EIP=004015d7 EFLGS=00010216
EBX=004015cd SS=013f ESP=0066f030 EBP=0066f790
ECX=00000100 DS=013f ESI=00890c30 FS=2367
EDX=8154e748 ES=013f EDI=0066f350 GS=0000
Bytes at CS:EIP:
8b 40 08 50 e8 21 4a 01 00 8b ce e8 bb 22 01 00
Stack dump:
00000030 00000000 0040a035 0066f04c 004015cd 004015cd
0066f790 0066f0c8 00408010 004015cd 0066f784 00000100
0066f0b8 00408030 0041fae0 0066f784
David O. Ohlssen
I _____________________________________ I
I | Davido@Commerce.CTech.ac.ZA | I
I | __ ____________ | I
I | / \/ Cape Town \ _ | I
I |__/ South Africa \/ \__________| I
I_________________________________________I
Mike Blaszczak -- mikeblas@interserv.com
Wednesday, February 07, 1996
[Mini-digest: 2 responses]
On Tue, 6 Feb 1996, "David Ohlssen" wrote:
>Hows this:
>Stack dump:
>00000030 00000000 0040a035 0066f04c 004015cd 004015cd
>0066f790 0066f0c8 00408010 004015cd 0066f784 00000100
>0066f0b8 00408030 0041fae0 0066f784
Not very useful.
The numbers are meaningless because I (we) have no way of knowing what loaded
where on your machine. If, on the other hand, you use the VC++ debugger,
you'll get a stack trace that has symbols in it. That would make it possible
to tell what routine called what routine (with what parameters!) before the
crash happened.
.B ekiM
--
TCHAR szDisc[] = _T("These words are my own; I do not speak for Microsoft.");
-----From: "jeffg"
I have something similar, except that we are not using DAO. Under
WinNT the program works fine in both Release and Debug modes. The same
program under Win95 works fine under Release mode, but gets a Stack
Overflow in Debug mode. The way I have gone around this for the time
being is to compile up a single-threaded version of MFC and link that
in instead of the multi-threaded library. However, when we go to
threaded execution, this will no longer be an option. If you're not
using threads, you may want to try this to see if it helps.
______________________________ Reply Separator _________________________________
Subject: Re:Stack Dump- NT DAO prog crashes on W95
Author: mfc-l@netcom.com at Internet
Date: 2/7/96 2:21 PM
> >It's impossible to answre this question without a stack trace and
> >more information about the invalid memory access.
> >.B ekiM
Hows this:
It happens when I press the button to open the DAO recordset using
.Open() without parameters. The open has a try{}catch{} around it.
If I remember, the message was different when I did not have the
try/catch. Compiled on NT, trying to run on W95. All OK on NT.
TES953
caused an invalid page fault in module TES953.EXE at 0137:004015d7.
Registers:
EAX=00000000 CS=0137 EIP=004015d7 EFLGS=00010216
EBX=004015cd SS=013f ESP=0066f030 EBP=0066f790
ECX=00000100 DS=013f ESI=00890c30 FS=2367
EDX=8154e748 ES=013f EDI=0066f350 GS=0000
Bytes at CS:EIP:
8b 40 08 50 e8 21 4a 01 00 8b ce e8 bb 22 01 00
Stack dump:
00000030 00000000 0040a035 0066f04c 004015cd 004015cd
0066f790 0066f0c8 00408010 004015cd 0066f784 00000100
0066f0b8 00408030 0041fae0 0066f784
David O. Ohlssen
I _____________________________________ I
I | Davido@Commerce.CTech.ac.ZA | I
I | __ ____________ | I
I | / \/ Cape Town \ _ | I
I |__/ South Africa \/ \__________| I
I_________________________________________I
| Вернуться в корень Архива
|