User forums > Nightly builds
The 25 August 2012 build (8248) is out.
stefanos_:
@jens: I have compiled svn-8322 on Debian wheezy (32-bit) and crashed upon closing a project. I did not compile it with 2.9.x as I said I would, but decided to do the standard compilation process for now. I have attached the crash report and i hope it helps a bit.
ollydbg:
--- Quote from: stefanos_ on September 01, 2012, 03:07:48 pm ---@jens: I have compiled svn-8322 on Debian wheezy (32-bit) and crashed upon closing a project. I did not compile it with 2.9.x as I said I would, but decided to do the standard compilation process for now. I have attached the crash report and i hope it helps a bit.
--- End quote ---
I see no stack info in the crash report. :)
stefanos_:
well, whatever the system generated, i copied it and pasted it in a .txt file and attached it here. also, as i have already stated in a previous comment, when Code::Blocks is crashing on a UNIX-like environment, it would be nice to let user save the report somewhere and not place it in tmp directory which gets deleted upon Code::Blocks's closing.
It sounds silly isn't it? Strange, but now I see a generated folder with dbgrpt name and timestamp that has the codeblocks.xml file in it.
ollydbg:
--- Quote from: stefanos_ on August 29, 2012, 07:47:30 am ---greetings everyone.
I have built svn-8251, and when I right-click on a Headers / Sources sub-folder in Manager to remove files, it crashes.
Below you can find as an attachment the crash report.
System Specs:
OS = Windows XP SP3 [32-bit]
Compiler: TDM's GCC (the latest available)
wxWidgets = 2.8.10
--- End quote ---
I'm not sure which c::b did you run? To catch the bug, I suggest you can run the c::b under devel folder, because it has debug information there, so when it crashes, it will have file and line info in the backtrace report. :)
ollydbg:
--- Quote from: Agetian on August 27, 2012, 04:29:34 pm ---Sure thing, it's really a very simple test though, the entire test project that works as a test case consists of one file which is as follows:
--- Code: ---#include <iostream>
using namespace std;
int main()
{
string s = "Test";
cout << s << endl;
return 0;
}
--- End code ---
The breakpoint is set on the "cout << s << endl" line. I think it most surely is a gcc/gdb/mingw issue though, cause 4.6.1 works fine and 4.7.1 doesn't. I have, in addition to everything else, made double sure that I'm generating debugging symbols and that no optimizations are set, so it looks like a bug in gcc/gdb... Thanks for your desire to look into it!
--- End quote ---
I found the reason from gdb IRC, see below:
--- Quote --- ollydbg I have a problem under windows: gcc 4.7.x gdb-cvs, when try to show a std::string, I enter the command: output s.c_str(), but gdb response: Cannot evaluate function -- may be inlined
ollydbg what cause this kind of problem? thanks
ollydbg For the record, if gcc 4.6.x does not have such issue.
jankratochvil Try to use this function in the program, be sure to use -O0 -g (and not -O2 -g) and try -fkeep-inline-functions.
ollydbg OK, I will try this soon
ollydbg Hi, jan, thanks, it works.
ollydbg In-fact, I'm forum Code::blocks forum, we use such script to show the std::string value: output s.c_str()[0]@s.size()
ollydbg But, if the user does not expicit call the c_str() and size() in there code, gdb will report failure in running such script.
ollydbg That's strange, does gcc changed something?
ollydbg BTW: If I enable the python pretty printer, then I have no such issue, the str::string's content shown correctly either under gcc 4.7.x or gcc 4.6.x
jankratochvil Newer gcc has more optimizations, it has the right to do these optimizations. And sure Pretty Printers do not depend on inferior function calls, so that Pretty Printers can work also on core files.
ollydbg Ok, thanks, I will forward your explanation to Code::blocks forum, many thanks.
ollydbg So, it looks like gdb pretty-printer is the most suggest way to show std::string like contents, other gdb script are not suggest because they will cause such issue.
--- End quote ---
So, I suggest you can use gdb python pretty printer to show the value, they work OK with gcc 4.6.x and 4.7.x.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version