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 Message ----- From: "Lin Rongrong" <wo...@palmmicro.com> To: <sdcc-user@lists.sourceforge.net> Cc: <supp...@palmmicro.com> Sent: Wednesday, February 29, 2012 10:51 PM Subject: Re: Caught signal 11: SIGSEGV > 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://palmmicro.com/woody/ > > ----- Original Message ----- > From: "Lin Rongrong" <wo...@palmmicro.com> > To: <sdcc-user@lists.sourceforge.net> > Sent: Wednesday, February 29, 2012 4:24 AM > Subject: Re: Caught signal 11: SIGSEGV > > >> 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/ >>> >> > ------------------------------------------------------------------------------ Virtualization & Cloud Management Using Capacity Planning Cloud computing makes use of virtualization - but cloud computing also focuses on allowing computing to be delivered as a service. http://www.accelacomm.com/jaw/sfnl/114/51521223/ _______________________________________________ Sdcc-user mailing list Sdcc-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sdcc-user
