comp.lang.idl-pvwave archive - RDF feed
type: channel
description: Messages from Usenet group comp.lang.idl-pvwave, compiled by Paulo Penteado
items: Re: IDL 8.2+ Segmentation Fault / Abort on OSX with Dual-Thunderbolt Displays

Re: IDL 8.2+ Segmentation Fault / Abort on OSX with Dual-Thunderbolt Displays
type: item
description: On Friday, September 26, 2014 11:22:23 AM UTC-4, Joseph Hunkeler wrote: > On Thursday, September 25, 2014 6:22:59 PM UTC-4, Joseph Hunkeler wrote: >> Here goes... >> >> >> >> >> >> ## The Symptoms >> >> >> >> IDL 8.2+ immediately crashes at run-time if `LM_LICENSE_FILE` or `/Applications/exelis/license/license.dat` is populated. If neither the environment variable or the license file are present, IDL enters demo mode successfully. >> >> >> >> ### IDL 8.2 Crash Message >> >> >> >> >> >> $ idl >> >> IDL Version 8.2.3, Mac OS X (darwin x86_64 m64). (c) 2013, Exelis Visual Information Solutions, Inc. >> >> Segmentation fault: 11 >> >> [/bash] >> >> >> >> ### IDL 8.3 Crash Message >> >> >> >> >> >> $ idl >> >> IDL Version 8.3, Mac OS X (darwin x86_64 m64). (c) 2013, Exelis Visual Information Solutions, Inc. >> >> idl(3438,0x7fff736a7310) malloc: *** error for object 0xf07: pointer being freed was not allocated >> >> *** set a breakpoint in malloc_error_break to debug >> >> Abort trap: 6 >> >> [/bash] >> >> >> >> ## The Cause >> >> >> >> At run-time, if licensing data is provided by the end-user, IDL attempts to gather information about the local system's network interfaces (specifically the MAC address). In our case IDL crashes because we have two external Thunderbolt monitors connected to the computer. If we remove one of the external displays IDL is able to continue on and retrieve a license without incident. >> >> >> >> The system experiencing the crash has eleven network interfaces defined, consisting of Bluetooth (1), FireWire (2), WiFi (1), Thunderbolt Ethernet (2), On-board Ethernet (2), Bridge Adapters (2), and an IPSec VPN (1). Whether these interfaces are active or not means nothing, as IDL will try to poll each one for a valid MAC address. >> >> >> >> ### IDL 8.2 Backtrace >> >> >> >> The data left behind in /Library/Logs/DiagnosticReports was mildly useful with IDL 8.2. The "l_getid_hw" tried to read the hardware address of a given (unknown) ethernet device, …
creator: Joseph Hunkeler
date: 2014-10-24T21:00:48-00:00