User forums > Using Code::Blocks
SIGFPE crash when debug Excel dll
DrOli:
Partial Response:
1) From previous "Second" point, Re the "click in message window" (e.g. on warning/error etc), CB won't navigate (I think you call it "jump") to the relevant file/line cited by the warning/error.
As I had speculated, it is definitely something to do with GCC5.3.0/GBD7.10.1. When I point my MingW back to the older version (4.9.2/7.9), the "jumps" WORK.
No idea how to fix this in 5.3.0 (I played around with the "outparse" a bit, but it's beyond me), any thoughts would be appreciated.
BTW, at the moment, the "jumps" occur via a single click (when they work). Is there a way to have only double-click make the "jump"?
2) GDB Crash/Bug: I have filed a bug report Re the GDB breakpoint crashes. I have produced an entire suite of files, CB project, Excel AddIn, etc that demonstrate the bug. Not sure if you are interested, but I can upload those files for your attention also, if desired.
Also, even if no interest in the bug/crash testing bits, those files include a PDF with a couple sections explaining how to set-up CB for Debugging DLL's/Excel Add-Ins, etc. It is possible that, with some edits, CB might be able to make use of those docs for the benefit of others. Let me know.
3) Purely for fun, I had made a guess as to the meaning of your remark "TL;DR;", I wonder if you might confirm what that means?
Cheers
tigerbeard:
--- Quote from: DrOli on March 30, 2016, 09:52:23 pm ---3) Purely for fun, I had made a guess as to the meaning of your remark "TL;DR;", I wonder if you might confirm what that means?
Cheers
--- End quote ---
I would guess TooLong Didnt Read...
Always difficult to hit the balance between giving enough details vs. wast peoples time. Having the problem all the time... 8)
DrOli:
Cheers for that.
Re the "no jump" error when clicking on warnings/errors in the Messages window, it seems when the "jumping" is broken, the line numbers are wrong also. I have attached a jpg showing line numbers in the 2nd to left column that clearly don't have anything to do with the actual line number as seen at the end of each message "line 46" vs. line 5443 ... hope that helps, the "(non) jumping" really needs to be fixed.
... assuming my memory is reliable :-)
Ta
oBFusCATed:
Can you post a minimal sample code that fails?
Also can you reproduce this with the c++ compiler?
DrOli:
Attached is a very simple project that fails (to jump) when I am using the GCC 5.3.0/ GDB 7.10.1 Toolchain.
In fact, after extensive testing, ALL but one of my CB Fortran projects fail to jump with 530/7101, but ALL of which WORK correctly with 492/79
I have only one C project in CB, and that works with both 492, and 530 etc.
I did find one Fortran project which works with 530. It is a very large project, so have not included it.
Though it may be red-herring, it is possible that the information on this page (https://gcc.gnu.org/gcc-5/changes.html) might be a hint, particularly around the line
"Incomplete support for colorizing diagnostics emitted by gfortran has been added" in the Fortran Section of the page.
Cheers
DrO
P.S. I have also included a (truncated) copy of the PDF I sent in with my GDB Crash/Bug report (GDB Crash Bug v0i_x.pdf). IT has a couple of sections that might be (after a little clean up) of use to CB for general distribution in relation to instructions on debugging DLL/Excel projects, and how to set-up CB for those cases. I understand you may be too busy, and might prefer to "switch to ignore" ... but if any of looks useful, I can always clean up the CB relevant Sections a bit for general consumption.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version