I have found this:
1 2
|
line = "</h2>" + line + "</h2>";
std::cout << line << std::endl;
|
This will stop the debugger - however maybe there is not error.
This will not stop the debugger but it will send SIGSEGV signal
1 2 3 4 5
|
sprintf(iStr, "%s", line.c_str() );
line += "<h2>";
line += iStr;
line += "</h2>";
getline (ifs, line);
|
I did not know what it means, but now I see it happens only when I watch the line. If I do not watch it, it will not send the SIGSEGV
3. it depends there I declare line. If I add it outside while loops on the begin of program, it will start to send SIGSEGV signal very early (because?) line was not initiated (?). This behaviour is strange. So I moved the declaration into while getline loop ... so the SIGSEGV is not displayed so early. It sucks because everytime it is displayed I see Stack Call window which takes 1/3 of my screen... Quite not comfortable debugging.
I am gonna to check your link now.
OK, I did your suggestion and checked the C++11. I did not know I can enable it! Thanks for it.
Now, when I have checked the compiler options it does not break here:
line = "<h2>" + line + "</h2>";
IDK what is going on here.
Do you know how to set hotkey for the Call Stack Window?