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 --std-c99 --max-allocs-per-node 
>> 9521 --codeseg
>> CODE5
>> Caught signal 11: SIGSEGV
>> Any idea of this singal 11?
> 
> Looks like a candidate for another bug report.
> 
> Philipp
> 
> ------------------------------------------------------------------------------
> All the data continuously generated in your IT infrastructure contains a
> definitive record of customers, application performance, security
> threats, fraudulent activity and more. Splunk takes this data and makes
> sense of it. Business sense. IT sense. Common sense.
> http://p.sf.net/sfu/splunk-d2d-oct
> _______________________________________________
> Sdcc-user mailing list
> Sdcc-user@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/sdcc-user


------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure contains a
definitive record of customers, application performance, security
threats, fraudulent activity and more. Splunk takes this data and makes
sense of it. Business sense. IT sense. Common sense.
http://p.sf.net/sfu/splunk-d2d-oct
_______________________________________________
Sdcc-user mailing list
Sdcc-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sdcc-user

Reply via email to