User forums > Nightly builds
The 25 August 2012 build (8248) is out.
stefanos_:
--- Quote from: ollydbg on September 01, 2012, 03:40:00 pm ---
--- 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. :)
--- End quote ---
ollydbg you must have confused my posts :) you commented for Debian wheezy issue on my Windows XP's post :D anyhow, i will try your suggestion on Monday when I will get back to work for I use Debian at home exclusively.
Agetian:
--- Quote from: ollydbg on September 01, 2012, 04:37:21 pm ---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.
--- End quote ---
Oh, thanks a lot for sorting this out, I'll try it out!
EDIT: Tried this out and it works perfectly! Thanks again! :)
stefanos_:
new awkward situation with svn-8322, Debian wheezy. On "Logs & Others", I right-clicked on a line from "Build Messages", select one of the options, or press the escape button, click anywhere with the mouse, it re-pops up the . Is that behavior normal? No it's not :)
oBFusCATed:
--- Quote from: stefanos_ on September 01, 2012, 10:34:07 pm ---new awkward situation with svn-8322, Debian wheezy. On "Logs & Others", I right-clicked on a line from "Build Messages", select one of the options, or press the escape button, click anywhere with the mouse, it re-pops up the . Is that behavior normal? No it's not :)
--- End quote ---
It is not normal, but it is not a new problem.
MortenMacFly:
--- Quote from: stefanos_ on September 01, 2012, 10:34:07 pm ---new awkward situation with svn-8322, Debian wheezy.
--- End quote ---
This seems a Linux only problem. On Windows it works as expected. Maybe a wx issue, not a C::B one.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version