some SSH on the playbook

I was able to use blackberry-connect to open up ssh access on my playbook. SCP'ed my mono install and received this error message:


Process 10866804 (mono) terminated SIGSEGV code=2 fltno=11 ip=000bfde0
Memory fault (core dumped)

Not sure what it means. I did some strange sig hacks, so I may start there. I wonder if i could use gdb to check out the core dump.

When i run Mono -V i get:


$ ./mono -V      
Mono JIT compiler version 2.10.9 (mono-2-10-9/256094a Mon May 28 09:15:52 EDT 2012)
Copyright (C) 2002-2011 Novell, Inc, Xamarin, Inc and Contributors. www.mono-project.com
TLS:           normal
SIGSEGV:       normal
Notification:  Thread + polling
Architecture:  armel,vfp
Disabled:      none
Misc:          softdebug
LLVM:          supported, not enabled.
GC:            none

I wonder if SIGSEGV has anything to do iwth it. Also, not sure about the architecture. is armel,vfp correct?


Comments

Post a Comment

Popular posts from this blog

So I've again been bitten by the Transcoding/transpiling bug...Doh! My history with Transcoding  A few years back (around mid-2007), I was enamored with a new language on the block, JavaFX (now vala). Alas, I had moved on from the Java platform to the .Net platform during that time, and Silverlight just hit the stage (and WPF). I was more of a fan of the declarative and expressive nature of JavaFX than I was of XAML, so I looked into porting JavaFX script to the .Net platform (and later the DLR). I halted my work in 2008-2009, as JavaFX script was dying, and the Parser technology I was using (a great C# based parser called Irony) was giving me issues when integrating with the DLR. The LLVM Project I've been a fan of the LLVM project since about 2009. I have also watched its MSIL backend go into disrepair and interest in C# as part of the vmkit wane. I answered some stack overflow questions in 2011 about this http://stackoverflow.com/questions/5054938/how-to-translate-
Read more

AutoConf and M4 bliss

Just wanted to make a statement that the CLI tooling for building software in linux (and really any *nix) has changed dramatically. In my mind, configure and make were all black boxes and it was very very hard to actually effect them as an independent developer once they were baked. This is not the case anymore. I was able, with autoconf, automake, and m4 templates (and of course some C++ glue) to actually integrate two libraries (zfs and snappy-c) that know nothing about each other. This is a testament not just to the auto tooling, but the level of maturity of a lot of open source software out there. While make is still technically a black box (yes, make scripts are simple in concept, fine...but go look at Illumos makefiles and we'll talk...), it may be ok for make to stay in the shadows...like some x86 assembly that gets generated on the fly... I just might, after this zfsonlinux + snappy release, revisit illumos. But from what I recall of the original opensolaris documentati
Read more