any work around for this bug with GDB?

[jack616]

I am using Typhon32  V4.6 on win7-64

I am experiencing the bug described here:
http://sourceware.org/bugzilla/show_bug.cgi?id=14018

Whereby GDB is failing to notice debug points and also
producing all the above described symptoms including the register
not available one (winerr 5)

I tried running the test button on the project options/Debugging panel
(though I dont understand what it tests exactly) and that reports
an error : Fatal syntax error "BEGIN" expected but "end of file" found
I dont know if that is relevant.
The line before the error reads : Parsing implementation of .... \testcompileroptions.pas
I will try changing various options on the off chance that highlights the  problems

My application builds/compiles and runs fine - I am debugging to adjust
things not because anything isnt working.

If it is relevant the application is one I have converted from delphi-5.
I had to remove all the UTF8 references the converter puts in again because they
just dont work.

Any suggestions to get debugging working would be welcome.

TIA

[Martin_fr]

As for the "(winerr 5)", I do not know if there is a good gdb version for 64 bit. IF you can find a stable GDB 7.2 then that should work.

Or you build 32 bit apps for debugging, and use the 32 bit gdb 7.2-1 that ships with Lazarus 32 bit.

1.2RC1 comes with the ability to build 64 and 32 bit for Windows from the same IDE.

[jack616]

Thanks Martin - It does look like this is a recurrent problem with GDB
A much earlier version may well be the answer -
I spent all day yesterday
trying to get a string grid working only to find out its something GDB did when it
crashed that cause the entire system to act oddly(thereby confusing me about string grids)
When it crashes the only
way out is to use windows task manager to kill lazarus entirely and it
seems to do something it shouldnt be able to  that remains when it happens.
A cold boot seems advisable every time.
It is repeatable so hopefully someone will find out the cause sooner or later.

I've reverted to Typhon V4.5 and found this still happens with the earlier GDB they used
but not nearly as badly. It also seems related to the application being developed - maybe
the components used or something.

As you suggest maybe GDB 7.2 is the best answer - but its time wasting again ...
trying to get a working one then integrating it and fixing whatever turns up while doing it...etc.

Engage Marvin mode:
Life  ... don't talk to me about life...