With #6969 build, my sips.c compiled correctly with "--max-allocs-per-node
9521" and compiled wrong with "--max-allocs-per-node 9522", so I was moving
functions out of sips.c to see which function compiled wrong. All of a
sudden, this "Caught signal 11: SIGSEGV" came out after I moved some
func
That looks like a bad pointer reference to me
Segment Violation...
dwg
On Oct 16, 2011, at 11:49 AM, Philipp Klaus Krause wrote:
> Am 16.10.2011 18:15, schrieb Lin Rongrong:
>> While I am trying to locate the bug of this problem, I got the following:
>> C:\SDCC\BIN\sdcc sips.c -mz80 -c --st
It was generated from a temp file while I was tracking bug 3424436 in the
past 10 hours. It appeared only once, and when file contents changed, it
disappeared, and I was not sensitive enough to keep a copy of it.
Woody
http://palmmicro.com/woody/
- Original Message -
From: "Philipp Kl
Am 16.10.2011 18:15, schrieb Lin Rongrong:
> While I am trying to locate the bug of this problem, I got the following:
> C:\SDCC\BIN\sdcc sips.c -mz80 -c --std-c99 --max-allocs-per-node
> 9521 --codeseg
> CODE5
> Caught signal 11: SIGSEGV
> Any idea of this singal 11?
Looks like a candidate for a
While I am trying to locate the bug of this problem, I got the following:
C:\SDCC\BIN\sdcc sips.c -mz80 -c --std-c99 --max-allocs-per-node
9521 --codeseg
CODE5
Caught signal 11: SIGSEGV
Any idea of this singal 11?
Woody
http://palmmicro.com/woody/
- Original Message -
From: "Philipp Kl
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Am 16.10.2011 07:47, schrieb Lin Rongrong:
> Another bad news, something related with SIP compiled wrong
> during --max-allocs-per-node increased from default 3000 to 1.
> With default 3000, my software works ok so far, with 1, SIP calling out
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Am 16.10.2011 07:18, schrieb Lin Rongrong:
> Results tried with "--oldralloc":
> code0 data code1 code2 code3 code4 code5 code6 code7 code
> 1C8D 1A90 4661 525B 47A7 50A5 55D0 4354 5625 1BB0 // ar168g sip
> 0.55.006 sdcc 3.0.1
> 1BFC 1A9
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Am 16.10.2011 06:29, schrieb Lin Rongrong:
> Philipp,
>
>I tested current build #6969, all fine so far. And I noticed that the
> compile time was almost the same as 3.0.1 now, and the code size vary on
> different code:
>
> code0 datacode1
Dear sdcc users,
I'm pleased to announce that the SDCC 3.1.0 is planed to be released on
2011-11-26.
*SDCC 3.1.0 release is dedicated to memory of Dennis M. Ritchie, father
of the C programming language.*
More info at
https://sourceforge.net/apps/trac/sdcc/wiki/SDCC%203.1.0%20Release
Bor