First-chance exception in secantTests.exe (KERNEL32.DLL): 0xE06D7363:
Microsoft C++ Exception.
The engineers at this third-party have not been able to reproduce the
problem and, as yet, do not know what the problem is.
How can I find out what the offending routine is within kernel32.dll? Is
there a memory map that I can refer to. I tried looking at the dll with
Quick View but the addresses seem not be load addresses as the above message
seems to imply.
Help.
Victor Ortiz.
> How can I find out what the offending routine is within kernel32.dll?
Grab your NT CD. In the directory \support, grab the symbols tree and
copy it to %systemroot% such that you end up with
+ winnt (or whatever)
|
+ symbols
|
+ dll
|
+ exe
|
+ drv
and so on. Then, grab the symbols for your latest installed service pack
(usually from the same place where you got the SP and update the files
from the NT CD.
Of course, if all you are interested in is kernel32, you only need that
one symbol file.
In general, though, what you need are not kernel32 symbols. You want the
3rd-party lib's symbols instead so the "engineers" of that company can
look what they are doing when things go pear-shaped.
--
Cheers,
Felix.
If you post a reply, kindly refrain from emailing it, too.
Note to spammers: fel...@mvps.org is my real email address.
No anti-spam address here. Just one comment: IN YOUR FACE!
KERNEL32! RaiseException@16 + 106 bytesHTH
MSVCRTD! _CxxThrowException@8 + 57 bytes
CFooDlg::OnMisbehave() line 73
...
-- Aaron [MVP]
---------------------
Aaron J Margosis
aaro...@erols.com
Victor Ortiz wrote:
I am using a third-party library which accesses MSSQL via ODBC. My OS is NT
4.0 sp4 and I am writing an app using MSVC 6.0. I am evaluating this
library and putting it through its paces. However, I am getting an
exception thrown into my scope with an accompanying message in the OUTPUT
window of the MSVC IDE.
First-chance exception in secantTests.exe (KERNEL32.DLL): 0xE06D7363:
Microsoft C++ Exception.
The engineers at this third-party have not been able to reproduce the
problem and, as yet, do not know what the problem is.
How can I find out what the offending routine is within kernel32.dll? Is