Author Topic: When loading core file, call stack of threads mixed together.  (Read 1719 times)

lambertia

  • Senior Community Member
  • Posts: 382
  • Hero Points: 14
  • I have nothing sufficiently witty to say.
When loading core file, call stack of threads mixed together.
« on: October 09, 2014, 12:05:52 am »
Hi!

Take a look at the pictures. The first is the stack first shown when the core file is loaded. It seems to be mixing mulitple threads together. The second is the correct call stack of the thread that aborted.

--

SlickEdit 2014 (v19.0.0.9 32-bit)

Serial number: FE10194_BETA
License type: Beta License
License expiration: 2014-10-23 12:17:00
License file: /opt/slickedit-19.0.0.9/bin/slickedit.lic

Build Date: September 29, 2014
Emulation: Brief

OS: Linux
OS Version: Ubuntu 10.04.4 LTS
Kernel Level: 3.13.0-36-generic
Build Version: #63-Ubuntu SMP Wed Sep 3 21:30:07 UTC 2014
Processor Architecture: i686

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

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

Installation Directory: /opt/slickedit-19.0.0.9/
Configuration Directory: /space/gbarron/work/mo-strategy/se/sc/19.0.0/


Dennis

  • SlickEdit Team Member
  • Senior Community Member
  • *
  • Posts: 3401
  • Hero Points: 465
Re: When loading core file, call stack of threads mixed together.
« Reply #1 on: October 09, 2014, 12:24:01 am »
There were some issues with the thread drop-down on the stack form, so I wouldn't be surprised if that was the cause of the problem you are seeing.  The problems should be fixed for the next drop, but if you want to send that core file into support so that I can test, I'd be happy to do that.

lambertia

  • Senior Community Member
  • Posts: 382
  • Hero Points: 14
  • I have nothing sufficiently witty to say.
Re: When loading core file, call stack of threads mixed together.
« Reply #2 on: October 09, 2014, 12:26:00 am »
Don't you ever sleep? I'm happy to wait for the next drop - if its not fixed then I'll send a core in. There is an easy workaround so I'm not fussed.