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++ / September 2007

Tip: Looking for answers? Try searching our database.

Release version crashes on the Multi-CPU system

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
David Yang - 24 Sep 2007 01:38 GMT
I have a C++/C++.net application. Release version crashes on the Multi-CPU
box but Debug version works well. And release version works well on
single-cpu box.

Any idea?
Doug Semler - 24 Sep 2007 02:44 GMT
>I have a C++/C++.net application. Release version crashes on the Multi-CPU
> box but Debug version works well. And release version works well on
> single-cpu box.
>
> Any idea?

As I tell my coworkers:

More information is needed than just "my application crashes".  What is the
error message?  Are you getting an exception?  Is it hanging?  Is it a GUI
program that's doing cross thread calls into controls improperly?  Have you
attached a debugger to the release version and tried trapping the exception?
Are you a multithreaded app, and if so are you using shared resources
properly (i.e. volatile members, locks, monitors, Interlocked increments,
etc).

It's probably a cross thread variable examiniation that isn't interlocked
properly on the multiprocessor machine or a cross thread GUI call.

Signature

Doug Semler, MCPD
a.a. #705, BAAWA.  EAC Guardian of the Horn of the IPU (pbuhh).
The answer is 42; DNRC o-
Gur Hfrarg unf orpbzr fb shyy bs penc gurfr qnlf, abbar rira
erpbtavmrf fvzcyr guvatf yvxr ebg13 nalzber. Fnq, vfa'g vg?

JP - 25 Sep 2007 01:44 GMT
Yup, one would require other information to even tell what is happening.

Basically it is always good to give callstack of the failing application and
as Doug said, more information will be always useful to give fast resolution.
Atleast that was my experience when I was a support engineer in VC/C# support
team.

> >I have a C++/C++.net application. Release version crashes on the Multi-CPU
> > box but Debug version works well. And release version works well on
[quoted text clipped - 14 lines]
> It's probably a cross thread variable examiniation that isn't interlocked
> properly on the multiprocessor machine or a cross thread GUI call.

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.