Re: [Sdcc-user] Caught signal 11: SIGSEGV

2012-03-15 Thread Lin Rongrong
Sorry I really do not mean to spam the mailing list with Caught signal 11: SIGSEGV. But I meet it again with: C:\sdcc\src>..\bin\sdcc -v SDCC : mcs51/gbz80/z80/z180/r2k/ds390/pic16/pic14/TININative/ds400/hc08 3.1.3 #7453 (Mar 15 2012) (MINGW32) C:\SDCC\BIN\sdcc sips.c -mz80 -c --std-c99 --max-al

Re: [Sdcc-user] Caught signal 11: SIGSEGV

2012-03-03 Thread Lin Rongrong
With build #7393, caught signal 11 again: C:\SDCC\BIN\sdcc function.c -mz80 -c --std-c99 --codeseg CODE1 Caught signal 11: SIGSEGV sdcpp.exe: fatal error: when writing output to : No such file or directory ..\bin\make: *** [function.rel] Error 1 Woody http://palmmicro.com/woody/ - Original

Re: [Sdcc-user] Caught signal 11: SIGSEGV

2012-02-29 Thread Lin Rongrong
Still with build #7371, today one of my co-worker found the same Caught signal 11: SIGSEGV, however, he was using "--max-allocs-per-node 9521". Really a mistery for me: C:\SDCC\BIN\sdcc sips.c -mz80 -c --std-c99 --max-allocs-per-node 9521 --codeseg CODE5 Caught signal 11: SIGSEGV Woody http://

Re: [Sdcc-user] Caught signal 11: SIGSEGV

2012-02-28 Thread Lin Rongrong
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 t