Tracking down Signal codes

Ok. I've been trying to tracked down the error's meaning. specifically SIGSEGV code=2. I found it listed in the header file located at  sys/siginfo.h :

* SIGSEGV codes (si_addr == address of faulting memory reference)
 */
#define SEGV_MAPERR     1       /* Address not mapped */
#define SEGV_ACCERR     2       /* No permissions */
#define SEGV_STKERR     3       /* ?? Stack exception */
#define SEGV_GPERR      4       /* ?? General protection */
#define SEGV_IRQERR     5       /* ?? Interrupt handler fault */
#if defined(__EXT_QNX)
#define NSIGSEGV        5
#endif

It seems to be SEGV_ACCERR. No permissions. Very interesting. I am not sure what it is trying to access, or why i dont have permissions as a developer. Hmmm...


Update:  Found addr2line. seems like there are some errors in aot-compiler.c, and some errors in mini-arm.c. I may just do a disable-aot and focus on the mini-arm.c issue...


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
Finding Libc So,  as you know, I've been tooling around with the LLVM IR syntax and the Gold Parser framework. I have the scaffolding for the CIL conversion 90% done, and I am almost ready to parse the "Hello world" code found in the LLVM documentation. There is just one catch. In the Hello world, there is a call to an external standard io library function called puts() . Those fimilar with C/C++ would know that you include the standard header, #include <stdio> or #include <stdio.h> and you magically gain access to this function. Porting that specific line into CIL would be easy, i'd just replace any puts call with a WriteLine call included in the standard System Library. This is fine to get the sample code running, but it is not a solution going forward. I need to get a list of basic libc commands and rewrite them to work with the System library in the CLI. DotGnu Project Resurrected? Years ago (around 2003-2004), the GNU community was really int
Read more