Build #7371 no longer generate time.c "Caught signal 11: SIGSEGV" any more. But I meet a new one today: C:\SDCC\BIN\sdcc sips.c -mz80 -c --std-c99 --max-allocs-per-node 9522 --codeseg CODE5 Caught signal 11: SIGSEGV sdcpp.exe: fatal error: ..\bin\make: *** [sips.rel] Error 1 when writing output to : Invalid argument
Using "--max-allocs-per-node 9521" does not generate the problem. I am running the MINGW32 build on a 64bit Windows Vista. Woody http://palmmicro.com/woody/ ----- Original Message ----- From: "Lin Rongrong" <wo...@palmmicro.com> To: <sdcc-user@lists.sourceforge.net> Sent: Monday, February 27, 2012 11:54 PM Subject: Caught signal 11: SIGSEGV > When testing #7368 today (SDCC : > mcs51/gbz80/z80/z180/r2k/ds390/pic16/pic14/TININative/ds400/hc08 3.1.3 > #7368 (Feb 27 2012) (MINGW32)), I found one of my file time.c will get > following error with command line: > C:\SDCC\BIN\sdcc time.c -mz80 -c --std-c99 --max-allocs-per-node > 9522 --codeseg CODE1 > Caught signal 11: SIGSEGV > ..\bin\make: *** [time.rel] Error 1 > Then I started to get a "min" version of time.c to repeat the problem for > a new bug report. I separated the functions in time.c into 2 parts. Each > part of functions compiled ok. But when they merge into a single file, the > problem began. > What is this "Caught signal 11: SIGSEGV" actually about? Any suggestion > for me to locate and minimize the problem? > > Woody > > http://palmmicro.com/woody/ > ------------------------------------------------------------------------------ Keep Your Developer Skills Current with LearnDevNow! The most comprehensive online learning library for Microsoft developers is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, Metro Style Apps, more. Free future releases when you subscribe now! http://p.sf.net/sfu/learndevnow-d2d _______________________________________________ Sdcc-user mailing list Sdcc-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sdcc-user
