Oscilloscope startup command ends in ABORT with debug from GDB and SIGSEGV while executing native code

[Google Code Exporter]

What steps will reproduce the problem?
1. @raspberrypi ~ $ mono XOscillo.exe
2.
3.

What is the expected output? What do you see instead?
The following traceback:
Native stacktrace:


Debug info from gdb:

Cannot access memory at address 0x0
Cannot access memory at address 0x0
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/arm-linux-gnueabihf/libthread_db.so.1".
[New Thread 0x40949460 (LWP 5357)]
0x400fb7d0 in read () from /lib/arm-linux-gnueabihf/libpthread.so.0
  Id   Target Id         Frame
  2    Thread 0x40949460 (LWP 5357) "mono" 0x400fa700 in sem_wait@@GLIBC_2.4 () from /lib/arm-

linux-gnueabihf/libpthread.so.0
* 1    Thread 0x4002c000 (LWP 5356) "mono" 0x400fb7d0 in read () from 
/lib/arm-linux-

gnueabihf/libpthread.so.0

Thread 2 (Thread 0x40949460 (LWP 5357)):
#0  0x400fa700 in sem_wait@@GLIBC_2.4 () from 
/lib/arm-linux-gnueabihf/libpthread.so.0
#1  0x00195a40 in mono_sem_wait ()
#2  0x000ea384 in ?? ()
#3  0x000ea384 in ?? ()
Backtrace stopped: previous frame identical to this frame (corrupt stack?)

Thread 1 (Thread 0x4002c000 (LWP 5356)):
#0  0x400fb7d0 in read () from /lib/arm-linux-gnueabihf/libpthread.so.0
#1  0x400fb044 in __pthread_enable_asynccancel () from 
/lib/arm-linux-gnueabihf/libpthread.so.0
#2  0x00096e60 in ?? ()
#3  0x00096e60 in ?? ()
Backtrace stopped: previous frame identical to this frame (corrupt stack?)

=================================================================
Got a SIGSEGV while executing native code. This usually indicates
a fatal error in the mono runtime or one of the native libraries
used by your application.
=================================================================

Aborted

What version of the product are you using? On what operating system?


Please provide any additional information below.
Running Windows executable on Raspberry Pi with Debian Linux OS
Using Xming on Windows 7
XOscillo_20111215v7
Using Arduino Leonardo (board rev 3)
The .ino file loads into Arduino without error. Using your latest .ino file 
posted here.

Original issue reported on code.google.com by [e-mail] on 6 Jan 2013 at 4:33

[Google Code Exporter]

Ran XOscillo.exe from Windows XP sp3 machine and received an Application Error 
message window saying "The application failed to initialize properly 
(0xc0000135). Click OK to terminate the application.

Geo

Original comment by [e-mail] on 6 Jan 2013 at 1:26

[Google Code Exporter]

Woops! .NET v3.5 was not installed. Get a blank screen now, but need to connect 
a signal to the Arduino.

Geo

Original comment by [e-mail] on 6 Jan 2013 at 2:09

[Google Code Exporter]

Downloaded Arduino software from Arduino web site which included the USB serial 
port driver. Compiling samples and uploading from XP is working. Running 
XOscillo from Windows XP shows waiting for trigger.

Still cannot run XOcillo from Raspberry Pi Linux, see original posting with 
errors.

Original comment by [e-mail] on 6 Jan 2013 at 7:33

[Google Code Exporter]

http://www.raspberrypi.org/phpBB3/posting.php?mode=reply&f=66&t=11634

Looks like the issue is with floating point support in mono for Raspberry Pi 
being an armv6.

Original comment by [e-mail] on 6 Jan 2013 at 9:34

[Google Code Exporter]

Thanks! there is a new version though! :)

Original comment by [e-mail] on 8 Feb 2013 at 12:33