On Sep 14, 2016, at 11:28 AM, James Crate wrote: > With the update to v15.2, I am seeing crashes occurring in a compiled/built > standalone app. The crash log helpfully points out which process the crash is > occurring in, but it would be nice to get just a bit more information, like > which method and maybe even which line number. Is there a compiler directive > I can use to include debug symbols like the method name? > > For reference, here is a bit of the crash report. From looking at the stack > traces for other threads, it would appear that the actual 4D code is executed > at frame 4 of the stack trace. Frame 2 may be a call to a plugin? This code > does call a plugin (4D InternetCommands.bundle). However, while I could now > probably replace some of the 4D Internet Commands usage with the internal > HTTP commands, this process also uses the UDP commands to find the server, so > it would be helpful to have a bit more idea where to check. > > Crashed Thread: 10 Thea_Name_Updater (id = -5) > > Exception Type: EXC_BAD_ACCESS (SIGSEGV) > Exception Codes: KERN_INVALID_ADDRESS at 0x00000000ffffffff > Exception Note: EXC_CORPSE_NOTIFY > > [snip] > > Thread 10 Crashed:: Thea_Name_Updater (id = -5) > 0 com.apple.QD 0x9d8b282b SetGWorld + 38 > 1 4d.com.T17.app 0x0056bb76 CallUnPack(calcblock*, > short, long, char*, char***, long*, unsigned char) + 522 > 2 4d.com.T17.app 0x000c5b7b rt_RTCallExt + 3415 > 3 ??? 0x0cbef026 0 + 213839910 > 4 ??? 0x0f4625ed 0 + 256255469 > 5 4d.com.T17.app 0x004bf947 CallAsmPart2 + 59 > 6 4d.com.T17.app 0x000c7e08 > ExecPCodeWithParams(tRtGlobals*, tProcessGlobals*, long, long, long, > champvar_template<256>*) + 605 > 7 4d.com.T17.app 0x00344c8c > VDBLanguageContext_compiled::DoExecute(calcblock&, VCodeDescriptor*) + 126
From the above stack trace you can see it is crashing inside some QuickDraw code (com.apple.QD). And that call appears to be coming from a plugin. "rt_RTCallExt” is probably something like “runtime call call external" which is the old term for plugins. You mention using the 4D Internet Commands plugin. Of course 4D Internet Commands should not be doing any screen drawing and needing QuickDraw, unless it is trying to show a progress indicator. But this plugin is based on some super, super, super old code 4D got from PDM back in the early 90’s. Could be something in there that is causing the issue. Based on your comments and the crash log info, the finger is pointing in the direction of the 4D Internet Commands plugin. Have you opened a tech support case on this Jim? I think you should immediately. This is the kind of thing 4D Engineering needs to see and fix. And they can help you find an immediate workaround to stop the crashing while they fix the bug. If you open a tech support case they can get you access to a debug version of 4D that you can run. When it crashes it will point to the exact 4D command that was running when the crash occurred. I’ve done this and the crashing issue I had was resolved immediately after 4D engineering reviewed the the crash info and reported back “you are calling 4D xxx command in xxx method and that is where it crashed”. Tim ******************************************** Tim Nevels Innovative Solutions 785-749-3444 [email protected] ******************************************** ********************************************************************** 4D Internet Users Group (4D iNUG) FAQ: http://lists.4d.com/faqnug.html Archive: http://lists.4d.com/archives.html Options: http://lists.4d.com/mailman/options/4d_tech Unsub: mailto:[email protected] **********************************************************************
