From: Andrew Schetinin (AschetininENTOPIA.COM)
Date: Thu Apr 29 2004 - 02:22:46 CDT

• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

Hi Seshu,

One of the things that could help is having a proper call stack to
understand where it fails.
To get the call stack, you need connecting to MS Symbol Info Server.
Modern MS debuggers know how to download debug symbols for MS system
DLLs and generate a proper call stack.

You will need to download and install Debugging Tools for Windows, and
consult its help for configuring path to the symbol server. Usually, it
is an environment variable of a kind:

_NT_SYMBOL_PATH =
srv*c:\symbols*http://msdl.microsoft.com/download/symbols

If you have Visual Studio .NET (either of the versions), this will be
enough to get a very nice call stack with all system functions. I'm not
sure if VB knows to generate it, but VC++ does know for sure. Or you can
debug from WinDBG, which is more complex and unfriendly, but often
provide more useful info on the crash.

Best Regards,

Andrew

-----Original Message-----
From: Katiyar, Subodh (Path) [mailto:skatiyarAFSINDIA.COM]
Sent: Thursday, April 29, 2004 7:57 AM
To: DCOMDISCUSS.MICROSOFT.COM
Subject: Re: Help Needed

explain a bit about the dll
is it a com dll
or a application extention dll,also send the parameter definition you
are using along with the declares of the dll (in case it is a
application extention dll) regards

-----Original Message-----
From: Seshu Madabushi [mailto:SMadabushiISOFT.COM]
Sent: Wednesday, April 28, 2004 10:55 Shaam
To: DCOMDISCUSS.MICROSOFT.COM
Subject: Help Needed

Hello All

I am in a rather complex condition. I have a deadline to meet on Monday.
So please please help me.

Here is the situation: I have an application (VB app) talking to a DLL.
When I put the dll in debug mode and carry out some functions, I am
seeing exception in ntdll.dll and the call stack just shows a memory
location. I am unable to decipher this. Can anyone please tell me how to
exactly pinpoint where the problem is - I had seen in some discussion
boards that this is because of loose hanging pointers....

Had anyone seen this?

Thanks
Seshu

----------------------------------------------------------------
Users Guide http://discuss.microsoft.com/archives/mailfaq.html
contains important info. Save time, search the archives at
http://discuss.microsoft.com/archives/index.html . To unsubscribe,
mailto:DCOM-signoff-requestDISCUSS.MICROSOFT.COM

DISCLAIMER:
The information contained in this Message is confidential and intended
only for the use of the individual or entity identified. If the reader
of this message is not the intended recipient, any dissemination,
distribution or copying of the information contained in this message is
strictly prohibited. If you received this message in error, please
notify the sender immediately.

----------------------------------------------------------------
Users Guide http://discuss.microsoft.com/archives/mailfaq.html
contains important info. Save time, search the archives at
http://discuss.microsoft.com/archives/index.html . To unsubscribe,
mailto:DCOM-signoff-requestDISCUSS.MICROSOFT.COM

----------------------------------------------------------------
Users Guide http://discuss.microsoft.com/archives/mailfaq.html
contains important info. Save time, search the archives at
http://discuss.microsoft.com/archives/index.html .
To unsubscribe, mailto:DCOM-signoff-requestDISCUSS.MICROSOFT.COM

• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]