Loading ...
Sorry, an error occurred while loading the content.
 

Re: [zipitwireless] Possible hardware problems, program testers needed

Expand Messages
  • Michael Grigoni
    ... Never mind; it turns out that gcc -O -p is the culprit; compiling without profiling and optimization fixes it; I will try building with optimization
    Message 1 of 3 , Sep 1, 2006
      Michael Grigoni wrote:

      > Greetings:
      >
      > I am working on a port of 'heyu' (X10 automation) for the
      > Zipit; I am getting SIGABRTs and SIGSEGVs and each time
      > that I add some debug message printing, the fault moves
      > up in the code. I feel like I'm chasing a moving target
      > and I suspect memory or other hardware.
      >

      Never mind; it turns out that 'gcc -O -p' is the culprit;
      compiling without profiling and optimization fixes it;
      I will try building with optimization later. (gcc 3.3.1)

      Regards,

      Michael
    Your message has been successfully submitted and would be delivered to recipients shortly.