Program Keeps Crashing

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Run the xoscillo exe.
2. select new arduino
3. wait approx. 30 seconds, then it crashes, 

What is the expected output? What do you see instead?
None

What version of the product are you using? On what operating system?
downloaded the files today
Windows 7 x64

Please provide any additional information below.
when the program crashes her is the result of the "program has stopped 
responding window:

Description:
  Stopped working

Problem signature:
  Problem Event Name:   CLR20r3
  Problem Signature 01: xoscillo.exe
  Problem Signature 02: 1.0.0.0
  Problem Signature 03: 4ca72584
  Problem Signature 04: System
  Problem Signature 05: 2.0.0.0
  Problem Signature 06: 4a275e12
  Problem Signature 07: 3c55
  Problem Signature 08: b3
  Problem Signature 09: System.TimeoutException
  OS Version:   6.1.7600.2.0.0.256.1
  Locale ID:    1033

Read our privacy statement online:
  http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409

If the online privacy statement is not available, please read our privacy 
statement offline:
  C:\Windows\system32\en-US\erofflps.txt

Original issue reported on code.google.com by mitpatte...@gmail.com on 6 Oct 2010 at 5:42

[GoogleCodeExporter]

Even though you list the OS as X64 I tried xoscillo.exe on 32 bit XP and I get 
the same thing as above only with less info. Installing the windows debug tools 
to see what I can gather. If there is something specific you would like 
gathered, I'd be happy to gather it.

Original comment by standard...@gmail.com on 6 Oct 2010 at 10:27

[GoogleCodeExporter]

that that means it not a win7 issue or a 32 bit/64 bit issue, and the only 
reason i got so much info is the crash/program ending window in 7 shows a "show 
more info" so you don't have to look at logs or anything

Original comment by mitpatte...@gmail.com on 6 Oct 2010 at 10:30

[GoogleCodeExporter]

I modified the source code (my local copy) to check for bytes available before 
reading the serial data, as it was a serial timeout for me.  If you don't 
trigger the analog port in time it times out reading from the serial port.
Here is my read function in SerialArduino.cs

        public bool Read(byte[] readBuffer, int length)
        {
            int dataread = 0;
            while (dataread < length)
            {
                while (serialPort.BytesToRead == 0)
                {
                    System.Threading.Thread.Sleep(100);
                }
                dataread += serialPort.Read(readBuffer, dataread, length - dataread);
            }
            return true;
        }

Original comment by DanielLe...@gmail.com on 7 Oct 2010 at 12:41

[GoogleCodeExporter]

Interesting. I'd try it but the current distribution does not have source for 
the app.

Original comment by standard...@gmail.com on 7 Oct 2010 at 1:30

[GoogleCodeExporter]

I get a crash in about the same timeframe:

Faulting application name: XOscillo.exe, version: 1.0.0.0, time stamp: 
0x4ca72584
Faulting module name: KERNELBASE.dll, version: 6.1.7600.16385, time stamp: 
0x4a5bdfe0
Exception code: 0xc000041d
Fault offset: 0x000000000000aa7d
Faulting process id: 0x1ca8
Faulting application start time: 0x01cb65e549be72b0
Faulting application path: T:\DL\Arduino\XOscillo.exe
Faulting module path: C:\Windows\system32\KERNELBASE.dll
Report Id: a46d5196-d1d8-11df-9d40-001fd02923a5

Windows 7 x64. An Arduino with the firmware loaded is running on COM4:, ports 
in the system are COM1:, COM4:, COM29:

Screenshot attached.

Original comment by areweh...@gmail.com on 7 Oct 2010 at 6:14

Attachments:

• xoscilloproblem.png

[GoogleCodeExporter]

Hi, I meet similar problem on my NB
OS: Win XP, SP3
HW: Arduino Duemilanove w/ATmega168
Compiler: both 0018 & 0021
Error msg:
  EventType : clr20r3     
  P1 : xoscillo.exe     
  P2 : 1.0.0.0     
  P3 : 4ca72584
  P4 : system     
  P5 : 2.0.0.0     
  P6 : 4ba85929     
  P7 : 3c49     
  P8 : b3     
  P9 : system.timeoutexception 

Original comment by summer.w...@gmail.com on 8 Oct 2010 at 3:41

[GoogleCodeExporter]

Hey I just discovered today that you submitted this bug :-)

The arduino has a trigger option, and it only sends data when it detects the 
trigger condition. If the trigger condition doesnt happen for a while the 
client will timeout and I believe the time out is not handled very well... 

Coudl you try applying some signal to teh adc0 in teh arduino?

Thanks!

Original comment by aguav...@gmail.com on 7 Nov 2010 at 2:00

[GoogleCodeExporter]

If that fails, a good test is to try to connect to the arduino with a terminal 
program, then send this character '?', the arduino should reply with "OC" and 
some other data which doesnt matter right now, the important thing is to test 
whether you can talk successfully with the arduino

Original comment by aguav...@gmail.com on 10 Nov 2010 at 2:30

[GoogleCodeExporter]

I can confirm that the problem is lack of signal on the input. With a signal on 
the analog input when I create the new Arduino window it works for me. If I 
take away the signal it will crash (same error as before) after 7 seconds.

Original comment by areweh...@gmail.com on 10 Nov 2010 at 11:58

[GoogleCodeExporter]

Also built from the current source in VS2010 this issue doesn't happen, so I 
guess it has been fixed at some point? standardrockets the source is available 
from the location on the source tab using Mercurial.

Original comment by areweh...@gmail.com on 11 Nov 2010 at 3:27

[GoogleCodeExporter]

Awesome! I'll add it to a known issues list and it will be fixed on a future 
release

Original comment by aguav...@gmail.com on 14 Nov 2010 at 5:22

• Changed state: WontFix