|
|
Home » U++ TheIDE » U++ TheIDE: Other Features Wishlist and/or Bugs » theIDE segmentation fault [FIXED]
theIDE segmentation fault [FIXED] [message #4965] |
Sun, 27 August 2006 23:35  |
masu
Messages: 378 Registered: February 2006
|
Senior Member |
|
|
I get a core dump when doing the following with latest UVS2 sources (608.r21):
1. start theIDE
2. open any package
3. call Help Topics
4. try to open any other package
Matthias
931b81e7ea53320dccc37375b34b38c3
[Updated on: Wed, 01 November 2006 22:20] Report message to a moderator
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Re: theIDE segmentation fault [BUG] [message #5149 is a reply to message #5095] |
Fri, 08 September 2006 09:58   |
 |
mirek
Messages: 14255 Registered: November 2005
|
Ultimate Member |
|
|
Well, I had some other things to do during last days, but I would like to resolve this soon now.
The trouble is that I am still unable to reproduce the problem.
Do you think you could do some debuging efforts? Basically, the most effective way how to debug such release problems is to put RLOGs and RDUMPs into the code to find out which code does the crash, e.g.
void SyncTopicFile(const String& link, const String& path)
{
RLOG(path);
TopicInfo& ti = topic_info().GetAdd(link);
RLOG("1");
Time tm = FileGetTime(path);
RLIG("2");
if(ti.path == ":ide:" || ti.path == path && ti.time == tm)
return;
String fn = TopicCacheName(path);
RLOG("3");
if(FileGetTime(fn) > tm) {
RLOG("4");
ClearLinkRef(link);
RLOG("5");
....etc
This way you can find witch function does the crash, then repeat the process inside that function body...
Might look a bit tedious, but in fact is usually the fastest way how to debug similar release mode problems.
(BTW, I bet that at the end of process, it will be unitialized member variable 
Mirek
|
|
|
|
|
|
|
Goto Forum:
Current Time: Tue Apr 29 11:13:36 CEST 2025
Total time taken to generate the page: 0.04468 seconds
|
|
|