SIGILL from drawterm

Issue #3 resolved
Chris Vitale
created an issue

I'm running the latest drawterm-cocoa, which I built locally.

I had drawterm running in full screen mode and switched to another desktop.

I then got a SIGILL.

Comments (7)

  1. Jeff Sickel repo owner

    Any chance another host took over the address of your cpu? I just brought up another machine's /net interface with the same address as another (e.g. two machines sharing 192.168.1.103) and got this same panic. In this case (5 drawterm 0x000a0715 exportfs + 1109) it is a garbaged 9p message.

  2. Chris Vitale reporter

    All my IPs are dynamically allocated. I suppose it is possible that my dhcp server could have messed something up badly. I can't prove that there wasn't a duplicate IP at that moment.

    The sysfatal that was printed mentioned an illegal instruction.

  3. michaelian Ennis

    Running 2012-12-21 : d51dc9b833d7 I get a similar looking error. When I don't shut down drawterm before do something that changes my ip address. Go home at night for example. I see drawterm has crashed with a SIGILL Exception.

    Date/Time:       2013-01-24 09:55:17.768 -0500
    OS Version:      Mac OS X 10.8.2 (12C3006)
    
    Crashed Thread:  2  cpumain
    
    Exception Type:  EXC_BAD_INSTRUCTION (SIGILL)
    Exception Codes: 0x0000000000000001, 0x0000000000000000
    
    
    Thread 2 Crashed:: cpumain
    0   drawterm                        0x000d5ee3 dumpstack + 3 (stub.c:68)
    1   drawterm                        0x000b0507 dt_panic + 359 (devcons.c:192)
    2   drawterm                        0x00116e06 _sysfatalimpl + 390 (sysfatal.c:17)
    3   drawterm                        0x00116e5b sysfatal + 43 (sysfatal.c:30)
    4   drawterm                        0x000e0e13 fatal + 371 (exportfs.c:535)
    5   drawterm                        0x000e06e5 exportfs + 1109 (exportfs.c:111)
    6   drawterm                        0x000a2505 cpumain + 3893 (cpu.c:213)
    7   drawterm                        0x00110252 cpumainkproc + 66 (main-cocoa.m:47)
    8   drawterm                        0x000dfe6f tramp + 127 (posix.c:134)
    9   libsystem_c.dylib               0x98a65557 _pthread_start + 344
    10  libsystem_c.dylib               0x98a4fcee thread_start + 34
    
    
    
    Thread 2 crashed with X86 Thread State (32-bit):
      eax: 0x00197a00  ebx: 0xb0288c10  ecx: 0x000fc080  edx: 0x000dbbc0
      edi: 0xb0288480  esi: 0xb02885a4  ebp: 0xb0288448  esp: 0xb0288448
       ss: 0x00000023  efl: 0x00010286  eip: 0x000d5ee3   cs: 0x0000001b
       ds: 0x00000023   es: 0x00000023   fs: 0x00000023   gs: 0x0000000f
      cr2: 0xb02736ac
    Logical CPU: 1
    
  4. Jeff Sickel repo owner

    This issue can be addressed as we roll in updates from the linux branch. There are a few conditions like this where the crash log doesn't really help. We know that the connection went away, no need to dump the stats.

  5. Log in to comment