Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
HomeAnnouncementsFree MagazinesWhite PapersSubmit Content
Discussion GroupsASP.NETWindows FormsLanguages.NET FrameworkVisual Studio.NET
Articles.NET FrameworkASP.NETToolsWindows Forms
.NET DirectoryOpen Source ProjectsUser GroupsWeb Resources
Related Topics
Visual Basic 6SQL ServerMS AccessOther DB ProductsMS Server ProductsMore Topics ...

.NET Forum / Languages / Managed C++ / October 2004

Tip: Looking for answers? Try searching our database.

VC++, Windbg and appl verifier

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Itjalve - 22 Oct 2004 14:37 GMT
I have a heap problem in my com exe server.
When i use windbg as the compiler in application verifier is windbg started
and i can press 'g' and the server is running unitil i get the exception.

When i'm using VC.net i get an excpetion in the client which starts the
server! I have not added the client to appl verifier, so how come that VC is
launched with the client.exe?

And is it possible to load symbols after VC has started, i.e. like windbg
.reload?

/Tjalve
Oleg Starodumov - 22 Oct 2004 15:57 GMT
> I have a heap problem in my com exe server.
> When i use windbg as the compiler in application verifier is windbg started
[quoted text clipped - 3 lines]
> server! I have not added the client to appl verifier, so how come that VC is
> launched with the client.exe?

Do you mean that the client crashes with an exception before the server
has started under debugger?

If yes, debug the client and see where the exception is thrown.
It can be a bug in the client.

If the server cannot start under debugger, make sure that you enter the full path
to Devenv.exe followed by /debugexe in "Debugger" field in AppVerifier options
for the server executable (better if there are no spaces in the path).

If the server successfully starts under VS.NET debugger, and the client's call to the server
returns 0x80010105 error code, then you should configure VS.NET debugger
(the one that is launched to debug the server) to stop on first chance access violation
exceptions (Debug | Exceptions | Win32 Exceptions | Access violation, select
"When the exception is thrown" - "Break into debugger").

This is because by default the debugger does not stop on first chance access violations,
and the exception thrown by AppVerifier/PageHeap is handled by COM stub
and passed to the client as an error code.

Another way to achieve the same result is described here:
http://support.microsoft.com/default.aspx?scid=kb;en-us;198623

> And is it possible to load symbols after VC has started, i.e. like windbg
> .reload?

Yes, if symbols are not yet loaded. In Modules window, select the module
and R-Click + Reload Symbols.

Regards,
Oleg
Itjalve - 22 Oct 2004 17:43 GMT
Great thank you!

> > I have a heap problem in my com exe server.
> > When i use windbg as the compiler in application verifier is windbg started
[quoted text clipped - 35 lines]
> Regards,
> Oleg

Free Magazines

Get these publications absolutely FREE for up to 12 months. There are no hidden fees and no obligation. Simply choose a title, complete the application form and submit it. Read more ...

Oracle MagazineNetwork ComputingComputer WorldBio-IT WorldeWeekInformation WeekInfosecurity
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.