Overview
Examples
Screenshots
Comparisons
Applications
Download
Documentation
Tutorials
Bazaar
Status & Roadmap
FAQ
Authors & License
Forums
Funding Ultimate++
Search on this site
Search in forums












SourceForge.net Logo
Home » Developing U++ » U++ Developers corner » get debug info after intermittent crashing of theide
get debug info after intermittent crashing of theide [message #51114] Mon, 28 January 2019 09:10 Go to next message
slashupp is currently offline  slashupp
Messages: 231
Registered: July 2009
Experienced Member
(I don't know where else this should be posted)
(running on Linux)
At very irregular intervals theide crashes with "invalid memory access"
It happens, as far as I can remember, after I've compiled my app (in DEBUG)
and then click on the 'Execute'-button - my app still runs, but theide dissappears
(It happens with different apps at any stage of developemnt, not just one)

What can I do to get theide to log it's state & call-trace when this error happen?

(A last resort, because it is very intrusive, will be to run theide itself in DEBUG
but I would first like to try easier / less hassle methods before I go there.)

[Updated on: Mon, 28 January 2019 09:15]

Report message to a moderator

Re: get debug info after intermittent crashing of theide [message #51115 is a reply to message #51114] Mon, 28 January 2019 10:13 Go to previous messageGo to next message
mirek is currently offline  mirek
Messages: 13975
Registered: November 2005
Ultimate Member
slashupp wrote on Mon, 28 January 2019 09:10
(I don't know where else this should be posted)
(running on Linux)
At very irregular intervals theide crashes with "invalid memory access"
It happens, as far as I can remember, after I've compiled my app (in DEBUG)
and then click on the 'Execute'-button - my app still runs, but theide dissappears
(It happens with different apps at any stage of developemnt, not just one)

What can I do to get theide to log it's state & call-trace when this error happen?

(A last resort, because it is very intrusive, will be to run theide itself in DEBUG
but I would first like to try easier / less hassle methods before I go there.)


Log path is ~/.upp/theide/theide.log

Are you using trunk ide?

Mirek
Re: get debug info after intermittent crashing of theide [message #51116 is a reply to message #51115] Mon, 28 January 2019 11:28 Go to previous messageGo to next message
slashupp is currently offline  slashupp
Messages: 231
Registered: July 2009
Experienced Member
I'm using nightly build 12181
(I download & compile the most current nightly-build every now&then)

I did look at the log: '~/.upp/theide/theide.log' before I posted and it (still) contain the following:

Quote:
* /home/mais/bin/theide 28.01.2019 09:14:50, user: mais

09:14:50:884 INFO GuiMainFn_(): Version: 12181 (64 bit) (GCC) (C++11) (Gtk) Compiled: 08/25/ 18 09:35:37


I could not find out how to get more info into the log, so I posted my question
Re: get debug info after intermittent crashing of theide [message #51121 is a reply to message #51114] Tue, 29 January 2019 20:53 Go to previous message
Zbych is currently offline  Zbych
Messages: 325
Registered: July 2009
Senior Member
slashupp wrote on Mon, 28 January 2019 09:10

What can I do to get theide to log it's state & call-trace when this error happen?
(A last resort, because it is very intrusive, will be to run theide itself in DEBUG
but I would first like to try easier / less hassle methods before I go there.)


I guess you should build new binary with symbols (export CXXFLAGS="-ggdb -O3 -ffunction-sections -fdata-sections";export LDFLAGS="-ggdb"; make -j 4; make install) and enable core dump in your system.
After crash use gdb to find out the place when theide fails.

https://nanxiao.me/en/enable-generating-core-dump-file-on-de bian-linux/
https://stackoverflow.com/questions/5745215/getting-stacktra ce-from-core-dump

[Updated on: Tue, 29 January 2019 21:19]

Report message to a moderator

Previous Topic: Copying, installing, and using *.scd and *.udc speller dictionaries...
Next Topic: Large data ahead
Goto Forum:
  


Current Time: Fri Apr 19 19:30:51 CEST 2024

Total time taken to generate the page: 0.02493 seconds