gdl crashes mac air - how do I document?

Help
2014-07-29
2014-08-14
  • cosmicbruce

    cosmicbruce - 2014-07-29

    Hello:

    I have had 3 crashes of my mac air notebook while using gdl, but I have never had this kind of crash before, so it has to be gdl. I think this is a real bug, at least in installation. However, I'm sure it's of little use to tell the developers here "I had a crash", it needs to be documented. I'm not very system literate, so all I know is to look at the system log, and it's not informative; the string "gdl" does not appear, for example.

    So, if someone can tell me what information is required or useful for the developers, I presume I should get that information from wherever and put in a formal "ticket" for the bug. There is a message about a crash from "sophos", a virus scan program, but I don't see how that would be relevant.

    Here is what I know:

    • Complete system freeze occurs when gdl (apparently) at idle or when plotting. The freeze seems to be progressive, that is, some software works for a while but then one by one the apps die and then the system completely. Mac has a "force quit" utility that is usually very very bomb-proof, but not here, that was killed too.

    • gdl version: 0.9.4 install from macports

    • Hardware: Macbook Air, 13-inch, late 2010, Processor 2.13 GHz Intel Core 2 Duo, Graphics NVIDIA GeForce 320M 256 MB,

    • System: Software Mac OS X Lion 10.7.5 (11G63)


    ---------------------Syslog in relevant time period---------------

    Jul 29 12:49:05 10-93-e9-a-25-2a com.sophos.scan[255]: yontoo-e.ide zbot-iaj.ide zbot-iam.ide zbot-iba.ide zbot-ibl.ide zbot-ibr.ide zbot-ibu.ide zbot-ich.ide zbot-ick.ide
    Jul 29 12:49:05 10-93-e9-a-25-2a com.sophos.scan[255]: zbot-idb.ide zbot-ide.ide zbot-idk.ide zbot-ido.ide zbot-idp.ide zbot-iea.ide zbot-iek.ide zbot-iet.ide zbot-ifg.ide
    Jul 29 12:49:05 10-93-e9-a-25-2a com.sophos.scan[255]: zbot-ifh.ide zbot-ifj.ide zbot-ifk.ide zbot-igc.ide zbot-igf.ide zbot-igg.ide zbot-igk.ide zbot-igv.ide zbot-igy.ide
    Jul 29 12:49:05 10-93-e9-a-25-2a com.sophos.scan[255]: zbot-ihd.ide zbot-ihf.ide zbot-ihh.ide zbot-ihm.ide zbot-iht.ide zbot-ihx.ide zbot-iik.ide zbot-iio.ide zbot-iiv.ide
    Jul 29 12:49:05 10-93-e9-a-25-2a com.sophos.scan[255]: zbot-iix.ide zbot-ija.ide zbot-ijl.ide zbot-ikg.ide zbot-ikr.ide zbot-ikw.ide zbot-ilb.ide zbot-ilc.ide zbot-ile.ide
    Jul 29 12:49:05 10-93-e9-a-25-2a com.sophos.scan[255]: zbot-ilf.ide zbot-iln.ide zbot-ilt.ide zbot-imh.ide zbot-imi.ide zbot-imk.ide zbot-inc.ide zbot-ine.ide zbot-ink.ide
    Jul 29 12:49:05 10-93-e9-a-25-2a com.sophos.scan[255]: zbot-ino.ide zbot-int.ide zbot-inu.ide zbot-inv.ide zbot-inw.ide zbot-inx.ide zbot-inz.ide zbot-iod.ide zbot-iop.ide
    Jul 29 12:49:05 10-93-e9-a-25-2a com.sophos.scan[255]: zbot-iot.ide zbot-ipd.ide zbot-ipe.ide zbot-ipg.ide zbot-ipp.ide zbot-ipu.ide zbot-ipy.ide zbot-iqa.ide zbot-iqk.ide
    Jul 29 12:49:05 10-93-e9-a-25-2a com.sophos.scan[255]: zbot-iqo.ide zbot-iqs.ide zbot-iqt.ide zbot-iqu.ide zbot-iqv.ide zbot-irb.ide zbot-irc.ide zbot-iri.ide zbot-iro.ide
    Jul 29 12:49:05 10-93-e9-a-25-2a com.sophos.scan[255]: zbot-irv.ide zbot-rj.ide zbot-rp.ide zbotra-a.ide zegos-co.ide zegos-cs.ide zegos-cy.ide zegost-v.ide zemot-a.ide
    Jul 29 12:49:05 10-93-e9-a-25-2a com.sophos.scan[255]: zemot-d.ide zemot-e.ide zortob-a.ide
    Jul 29 12:49:05 10-93-e9-a-25-2a com.sophos.scan[255]: Jul 29 12:49:05 10-93-e9-a-25-2a.dhcp.lbnl.us scanserver[255] <Info>: Worker thread with context 0x10a5221a0 starting up
    Jul 29 12:49:07 10-93-e9-a-25-2a InterCheck[252]: Live protection is Enabled
    Jul 29 12:49:37: --- last message repeated 9 times ---
    Jul 29 12:51:00 10-93-e9-a-25-2a fseventsd[20]: SLOWDOWN: client 0x7f9ec1020200 (pid 90) sleeping due to too many errors (num usleeps 35)
    Jul 29 12:51:19 10-93-e9-a-25-2a [0x0-0x5005].com.apple.mail[145]: Range {0x0000, 0xFFFF} is not 1-dimensional; handling as a special case.
    Jul 29 12:51:37: --- last message repeated 9 times ---
    Jul 29 12:51:37 10-93-e9-a-25-2a SophosSXLD[242]: 20140729 195137.428 P 242 T 3006 ------ 1 ERROR: assertion 'sxl3_config_enable_ipv6' failed at sxl3-service.c:299; Error: cannot send DNS packet to server [2620:83:8000:140::3] when SXL3_ENUM_ATTRIBUTE_U32_CONFIG_ENABLE_IPV6 is false
    Jul 29 12:51:37 10-93-e9-a-25-2a SophosSXLD[242]: in function sxl3_start() at libsxl3/lib-sxl3-service/sxl3-service-api.c:146
    Jul 29 12:51:37 10-93-e9-a-25-2a ReportCrash[263]: DebugSymbols was unable to start a spotlight query: spotlight is not responding or disabled.
    Jul 29 12:51:38 10-93-e9-a-25-2a com.apple.launchd[1] (com.sophos.sxld[242]): Job appears to have crashed: Abort trap: 6
    Jul 29 12:51:38 10-93-e9-a-25-2a SophosSXLD[264]: sxl started
    Jul 29 12:51:38 10-93-e9-a-25-2a SophosSXLD[264]: sxl configuration succeeded
    Jul 29 12:51:38 10-93-e9-a-25-2a SophosSXLD[264]: daemon is running
    Jul 29 12:51:40 10-93-e9-a-25-2a ReportCrash[263]: Saved crash report for SophosSXLD[242] version ??? (???) to /Library/Logs/DiagnosticReports/SophosSXLD_2014-07-29-125140_localhost.crash
    Jul 29 12:51:40 10-93-e9-a-25-2a ReportCrash[263]: Removing excessive log: file://localhost/Library/Logs/DiagnosticReports/SophosSXLD_2014-07-29-110913_localhost.crash
    Jul 29 12:51:43 10-93-e9-a-25-2a SophosSXLD[264]: 20140729 195143.661 P 264 T 4129 ------ 1 ERROR: assertion 'sxl3_config_enable_ipv6' failed at sxl3-service.c:299; Error: cannot send DNS packet to server [2620:83:8000:140::3] when SXL3_ENUM_ATTRIBUTE_U32_CONFIG_ENABLE_IPV6 is false
    Jul 29 12:51:43 10-93-e9-a-25-2a SophosSXLD[264]: in function sxl3_start() at libsxl3/lib-sxl3-service/sxl3-service-api.c:146
    Jul 29 12:51:44 10-93-e9-a-25-2a com.apple.launchd[1] (com.sophos.sxld[264]): Job appears to have crashed: Abort trap: 6
    Jul 29 12:51:44 10-93-e9-a-25-2a com.apple.launchd[1] (com.sophos.sxld): Throttling respawn: Will start in 5 seconds
    Jul 29 12:51:44 10-93-e9-a-25-2a ReportCrash[263]: Saved crash report for SophosSXLD[264] version ??? (???) to /Library/Logs/DiagnosticReports/SophosSXLD_2014-07-29-125144_localhost.crash
    Jul 29 12:51:44 10-93-e9-a-25-2a ReportCrash[263]: Removing excessive log: file://localhost/Library/Logs/DiagnosticReports/SophosSXLD_2014-07-29-110934_localhost.crash
    Jul 29 12:51:45 10-93-e9-a-25-2a %s[83]: An exception was encountered while messaging the server: NSInvalidReceivePortException. Retrying: 1 attempt(s)
    Jul 29 12:51:49 10-93-e9-a-25-2a SophosSXLD[271]: sxl started
    Jul 29 12:51:49 10-93-e9-a-25-2a SophosSXLD[271]: sxl configuration succeeded
    Jul 29 12:51:49 10-93-e9-a-25-2a SophosSXLD[271]: daemon is running
    Jul 29 12:51:52 10-93-e9-a-25-2a SophosSXLD[271]: 20140729 195152.287 P 271 T 4373 ------ 1 ERROR: assertion 'sxl3_config_enable_ipv6' failed at sxl3-service.c:299; Error: cannot send DNS packet to server [2620:83:8000:140::3] when SXL3_ENUM_ATTRIBUTE_U32_CONFIG_ENABLE_IPV6 is false
    Jul 29 12:51:52 10-93-e9-a-25-2a SophosSXLD[271]: in function sxl3_start() at libsxl3/lib-sxl3-service/sxl3-service-api.c:146
    Jul 29 12:51:52 10-93-e9-a-25-2a com.apple.launchd[1] (com.sophos.sxld[271]): Job appears to have crashed: Abort trap: 6
    Jul 29 12:51:52 10-93-e9-a-25-2a com.apple.launchd[1] (com.sophos.sxld): Throttling respawn: Will start in 7 seconds
    Jul 29 12:51:52 10-93-e9-a-25-2a ReportCrash[263]: Saved crash report for SophosSXLD[271] version ??? (???) to /Library/Logs/DiagnosticReports/SophosSXLD_2014-07-29-125152_localhost.crash
    Jul 29 12:51:53 10-93-e9-a-25-2a ReportCrash[263]: Removing excessive log: file://localhost/Library/Logs/DiagnosticReports/SophosSXLD_2014-07-29-110938_localhost.crash
    Jul 29 12:51:53 10-93-e9-a-25-2a %s[83]: An exception was encountered while messaging the server: NSInvalidReceivePortException. Retrying: 1 attempt(s)
    Jul 29 12:51:54 10-93-e9-a-25-2a SophosWebD[83]: <SMENode: 0x7fb829e2c190=""> localNode csc:1ERROR! encountered an error while writing to outputstream| error:Error Domain=NSPOSIXErrorDomain Code=32 "The operation couldn’t be completed. Broken pipe" UserInfo=0x7fb829e3e230 {}
    Jul 29 12:51:59 10-93-e9-a-25-2a SophosSXLD[274]: sxl started
    Jul 29 12:52:00 10-93-e9-a-25-2a SophosSXLD[274]: sxl configuration succeeded
    Jul 29 12:52:00 10-93-e9-a-25-2a SophosSXLD[274]: daemon is running
    Jul 29 12:52:02 10-93-e9-a-25-2a SophosSXLD[274]: 20140729 195202.291 P 274 T 4627 ------ 1 ERROR: assertion 'sxl3_config_enable_ipv6' failed at sxl3-service.c:299; Error: cannot send DNS packet to server [2620:83:8000:140::3] when SXL3_ENUM_ATTRIBUTE_U32_CONFIG_ENABLE_IPV6 is false
    Jul 29 12:52:02 10-93-e9-a-25-2a SophosSXLD[274]: in function sxl3_start() at libsxl3/lib-sxl3-service/sxl3-service-api.c:146
    Jul 29 12:52:02 10-93-e9-a-25-2a com.apple.launchd[1] (com.sophos.sxld[274]): Job appears to have crashed: Abort trap: 6
    Jul 29 12:52:02 10-93-e9-a-25-2a com.apple.launchd[1] (com.sophos.sxld): Throttling respawn: Will start in 8 seconds
    Jul 29 12:52:02 10-93-e9-a-25-2a ReportCrash[263]: Saved crash report for SophosSXLD[274] version ??? (???) to /Library/Logs/DiagnosticReports/SophosSXLD_2014-07-29-125202_localhost.crash
    Jul 29 12:52:02 10-93-e9-a-25-2a ReportCrash[263]: Removing excessive log: file://localhost/Library/Logs/DiagnosticReports/SophosSXLD_2014-07-29-111001_localhost.crash
    Jul 29 12:52:10 10-93-e9-a-25-2a SophosSXLD[277]: sxl started
    Jul 29 12:52:10 10-93-e9-a-25-2a SophosSXLD[277]: sxl configuration succeeded
    Jul 29 12:52:10 10-93-e9-a-25-2a SophosSXLD[277]: daemon is running
    Jul 29 12:52:13 10-93-e9-a-25-2a SophosSXLD[277]: 20140729 195213.016 P 277 T 4868 ------ 1 ERROR: assertion 'sxl3_config_enable_ipv6' failed at sxl3-service.c:299; Error: cannot send DNS packet to server [2620:83:8000:140::3] when SXL3_ENUM_ATTRIBUTE_U32_CONFIG_ENABLE_IPV6 is false
    Jul 29 12:52:13 10-93-e9-a-25-2a SophosSXLD[277]: in function sxl3_start() at libsxl3/lib-sxl3-service/sxl3-service-api.c:146
    Jul 29 12:52:13 10-93-e9-a-25-2a com.apple.launchd[1] (com.sophos.sxld[277]): Job appears to have crashed: Abort trap: 6
    Jul 29 12:52:13 10-93-e9-a-25-2a com.apple.launchd[1] (com.sophos.sxld): Throttling respawn: Will start in 8 seconds
    Jul 29 12:52:13 10-93-e9-a-25-2a ReportCrash[263]: Saved crash report for SophosSXLD[277] version ??? (???) to /Library/Logs/DiagnosticReports/SophosSXLD_2014-07-29-125213_localhost.crash
    Jul 29 12:52:13 10-93-e9-a-25-2a ReportCrash[263]: Removing excessive log: file://localhost/Library/Logs/DiagnosticReports/SophosSXLD_2014-07-29-111037_localhost.crash
    Jul 29 12:52:21 10-93-e9-a-25-2a SophosSXLD[278]: sxl started
    Jul 29 12:52:21 10-93-e9-a-25-2a SophosSXLD[278]: sxl configuration succeeded
    Jul 29 12:52:21 10-93-e9-a-25-2a SophosSXLD[278]: daemon is running
    Jul 29 12:52:23 10-93-e9-a-25-2a SophosSXLD[278]: 20140729 195223.863 P 278 T 5102 ------ 1 ERROR: assertion 'sxl3_config_enable_ipv6' failed at sxl3-service.c:299; Error: cannot send DNS packet to server [2620:83:8000:140::3] when SXL3_ENUM_ATTRIBUTE_U32_CONFIG_ENABLE_IPV6 is false
    Jul 29 12:52:23 10-93-e9-a-25-2a SophosSXLD[278]: in function sxl3_start() at libsxl3/lib-sxl3-service/sxl3-service-api.c:146
    Jul 29 12:52:24 10-93-e9-a-25-2a com.apple.launchd[1] (com.sophos.sxld[278]): Job appears to have crashed: Abort trap: 6
    Jul 29 12:52:24 10-93-e9-a-25-2a com.apple.launchd[1] (com.sophos.sxld): Throttling respawn: Will start in 8 seconds
    Jul 29 12:52:24 10-93-e9-a-25-2a ReportCrash[263]: Saved crash report for SophosSXLD[278] version ??? (???) to /Library/Logs/DiagnosticReports/SophosSXLD_2014-07-29-125224_localhost.crash
    Jul 29 12:52:24 10-93-e9-a-25-2a ReportCrash[263]: Removing excessive log: file://localhost/Library/Logs/DiagnosticReports/SophosSXLD_2014-07-29-113710_localhost.crash
    Jul 29 12:52:25 10-93-e9-a-25-2a %s[83]: An exception was encountered while messaging the server: NSInvalidReceivePortException. Retrying: 1 attempt(s)
    Jul 29 12:52:32 10-93-e9-a-25-2a SophosSXLD[279]: sxl started
    Jul 29 12:52:32 10-93-e9-a-25-2a SophosSXLD[279]: sxl configuration succeeded
    Jul 29 12:52:32 10-93-e9-a-25-2a SophosSXLD[279]: daemon is running
    Jul 29 12:53:03 10-93-e9-a-25-2a fseventsd[20]: SLOWDOWN: client 0x7f9ec1020200 (pid 90) sleeping due to too many errors (num usleeps 47)

     
  • Sylwester Arabas

    Hi,

    It might not be of use here, but generaly a "backtrace" provides a lot of hints. To get it, you can run gdl from within gdb - the GNU debugger, i.e.:

    $ gdb gdl
    GDL> ...
    ...
    gdb> bt

    Anyhow, your system logs point to a /Library/Logs/DiagnosticReports/SophosSXLD_2014-07-29-125224_localhost.crash file which perhaps might give some more information on the sophos crash...

    HTH,
    Sylwester

     
  • Alain C.

    Alain C. - 2014-07-31

    Would be great if you can find the location of the issue
    or a reproducible way to

    Up to now, no similar crashes reported to us, on OSX or other OSes.

    (I am making intensive usage of GDL for computation
    with larges code and large data in the GNU/Linux world
    without issue, except in very specific case of pointer allocation,
    might be fixed since my pbs.)

    I don't like the way "top" is by default in OSX
    but maybe you can follow how the memory related to GDL is increasing with time
    in your OSX session ?

    Alain

    PS: I usually compiled GDL very easily "by hand" on OSX, the difficult part
    is Plplot. May be you can try on the CVS version ??

     
  • cosmicbruce

    cosmicbruce - 2014-08-14

    Eventually this just stopped without explanation. I apologize to all for the spam, however, I may have learned something new about system logs.
    -CB

     

Log in to post a comment.