AnsweredAssumed Answered

vrf vee.exe runtime error

Question asked by VRFuser on Mar 20, 2002
Try reading the following articles:

http://support.microsoft.com/default.aspx?scid=kb;EN-US;q192123

This one points to a versioning issue
http://support.microsoft.com/default.aspx?scid=KB;EN-US;q190536


Jeff Davis
Embedded Systems - CDI Technical Services
3137 E Elwood # 160
Phoenix, Arizona 85034
Phone: (602)431-4497 (x226)
Cell: (480)330-1431
Fax: (602)431-4435
http://www.cdicad.com

-----Original Message-----
From: Mitchell, Tom (T.P.) [mailto:TMITCHEL@visteon.com]
Sent: Thursday, March 21, 2002 7:50 AM
To: Vee Reflector (E-mail) (E-mail)
Subject: vrf vee.exe runtime error


Hi.

I'm getting an error  that I cannot find.  The error reads "Microsoft Visual
C++ Runtime Library    runtime error
program "C:program filesagilentvee pro 6.0vee.exe""

This happens on a regular basis.  I think, the VEE.EXE program is crashing,
not so much my application.  But, I haven't ruled out that my application
might be causing VEE to crash.

SYSTEM: Dell PC 400MHZ, 128MBytes RAM, WIN98 Second edition.  I had
originally put the program on a 200 MHZ PC, but I checked the CPU and Kernel
usage using system tools, and found that the KERNEL usage was at 100% all of
the time.  When I put the 400 MHz PC on it, the KERNEL  usage was at 96%.
But it still crashes.  VEE Pro 6.0.  System resources free 83%.

My application is this.  I have 2 PC's connected together by their serial
ports.  COM2 to COM2, PC #1 runs my basic test program and all of my rack
mounted test equipment.  PC#2 controls an instrument that sends CAN
(automotive protocol) messages.  This is the PC that is crashing (PC#2).  PC
#1 sends a text string (On COM 2)  to PC#2 telling PC#2 which message to
send out on the CAN bus.  PC#2 has 2 Four different treads that are not
connect together, but all have start buttons. 

Thread #1 is the loop program that send the CAN module #1 messages out to
the box on COM1. uses on cycle command of 0.175 seconds to loop messages

Thread #2 is the loop program that send the CAN module #2 messages out to
the box on COM1.  uses on cycle command of 1.0 seconds   to loop messages

Thread #3 is the loop program that reads the CAN bus messages from the box
on COM1.             uses on cycle command of 0.20 seconds  to loop messages

Thread #4 sits and waits until a message is received on COM2 from PC #1.
When it receives the message, variables used in thread #1 are changed in
thread #2.  So thread #2 sets the variables, and thread #1 gets the
variables.

I think that I have a memory leak problem.  The I/O config help mentions a
problem with msvcrt.dll causing a 4K memory leak every time it links.  Would
going to windows 2000 help?  Any way to help track this down?

I've tried setting the buffer size, and faster PC's.  Neither seamed to
help.  But, this program seams to run better (doesn't crash as often) when I
do not use thread #1 at 175ms cycle time.  Is 175ms cycle time too fast for
VEE?

Thanks!

Tom Mitchell
Visteon Corporation
Soon to be Autoliv
Software Validation/Product Assurance
ETC Room B116
17000 Rotunda Drive
Dearborn, MI 48121

Voice/FAX number (313) 755-2901

Text pager:(313) 795-2709
EMAIL:tmitchel@visteon.com        
text pager 3137952709@alphapage.airtouch.com



---------------------------------------------------------------------
This is the "vrf" maillist, managed by Majordomo.  To send messages to
this maillist, just email to "vrf@lvld.agilent.com".  Subscriptions and
unsubscriptions are done through the address "vrf-request@lvld.agilent.com".
If you need details, just send a message containing the text "help"
to "vrf-request@lvld.agilent.com".
---------------------------------------------------------------------

________________________________________________________________________
This email has been scanned for all viruses by the MessageLabs SkyScan
service. For more information on a proactive anti-virus service working
around the clock, around the globe, visit http://www.messagelabs.com
________________________________________________________________________
---------------------------------------------------------------------
This is the "vrf" maillist, managed by Majordomo.  To send messages to
this maillist, just email to "vrf@lvld.agilent.com".  Subscriptions and
unsubscriptions are done through the address "vrf-request@lvld.agilent.com".
If you need details, just send a message containing the text "help"
to "vrf-request@lvld.agilent.com".
---------------------------------------------------------------------

Outcomes