SlickEdit Community

Archived Read Only Forums => SlickEdit 2013 v18 beta => Topic started by: lambertia on April 29, 2013, 11:54:12 pm

Title: BUG: 18.0.0.5: Core dumped when exiting. CAS-63696-GJV8
Post by: lambertia on April 29, 2013, 11:54:12 pm
When I exit cleanly, SE closes the windows and then dumps core. A core file has been uploaded to the case number in the subject line.

SlickEdit 2013 (v18.0.0.5 32-bit)

Serial number: FE10194_BETA
License type: Beta License
License expiration: 2013-07-25 04:21:00
License file: /opt/slickedit-18.0.0.5/bin/slickedit.lic

Build Date: April 23, 2013
Emulation: Brief

OS: Linux
OS Version: Ubuntu 10.04.4 LTS
Kernel Level: 3.5.0-26-generic
Build Version: #42-Ubuntu SMP Fri Mar 8 23:18:20 UTC 2013
Processor Architecture: i686

X Server Vendor: The X.Org Foundation
Memory: 78% Load, 2462MB/3130MB Virtual
Shell Info: /opt/slickedit-18.0.0.5/bin/secsh -i
Screen Size: 1920 x 1080, 1920 x 1080

Project Type: Cpp
Language: .cpp (C/C++)

Installation Directory: /opt/slickedit-18.0.0.5/
Configuration Directory: /space/gbarron/work/se/mo-trunk/sc/18.0.0/

Title: Re: BUG: 18.0.0.5: Core dumped when exiting. CAS-63696-GJV8
Post by: lambertia on April 30, 2013, 06:33:38 am
I've noticed that when I exit the separate build window hangs around for a while and the core appears when it goes.
Title: Re: BUG: 18.0.0.5: Core dumped when exiting. CAS-63696-GJV8
Post by: lambertia on April 30, 2013, 06:46:55 am
Ok it looks like it dumps core on exit if you have a file open.
Title: Re: BUG: 18.0.0.5: Core dumped when exiting. CAS-63696-GJV8
Post by: patrick on April 30, 2013, 01:20:23 pm
I believe this has been fixed for the next beta, but I'll double check it on 32 bit linux later this morning, for paranoia's sake.  Thanks for the report.
Title: Re: BUG: 18.0.0.5: Core dumped when exiting. CAS-63696-GJV8
Post by: patrick on April 30, 2013, 02:42:16 pm
I can't get the crash to happen with current beta 2 development build on 32 bit Unbuntu 11, so I think this is the same problem I fixed yesterday.  This should cover CAS-63688-QL9Z as well.  The problem was with with a common component, xmlcfg, and can only trigger on 32 bit builds.

We're shooting for having beta 2 out this Thursday, barring unforseen problems.