2010/12/8 Martin f...@mfriebe.de:
On 08/12/2010 21:22, Jonas Maebe wrote:
On 08 Dec 2010, at 21:32, Martin wrote:
Vincent did some tests with dwarf on win 64 bit.
with the lates (7.2.5) gdb and trunk results are fine = working.
but with fpc 2.4.2 instead there are strange errors:
It
In our previous episode, Vincent Snijders said:
Also I noticed that some revisions are not on that list, for example
r14068, probably because it is blocked, but its changes in dbgbase are
used in later revisions. So I got stuck.
I blocked some large revisions (and afaik Jonas has in the past
2010/12/13 Marco van de Voort mar...@stack.nl:
In our previous episode, Vincent Snijders said:
What would be the best way to proceed to identify the fixes in fpc
2.5.1 for DWARF info to be included in fpc 2.4.3 or a patched fpc
2.4.2?
Basically reviewing every commit to trunk since fixes_2_4
Vincent did some tests with dwarf on win 64 bit.
with the lates (7.2.5) gdb and trunk results are fine = working.
but with fpc 2.4.2 instead there are strange errors:
84. info address FPC_BREAK_ERROR
85. info address FPC_BREAK_ERROR\n
86. ~Symbol \FPC_BREAK_ERROR\ is at
On 08 Dec 2010, at 21:32, Martin wrote:
Vincent did some tests with dwarf on win 64 bit.
with the lates (7.2.5) gdb and trunk results are fine = working.
but with fpc 2.4.2 instead there are strange errors:
It simply means that there is an error in the DWARF info generated by FPC 2.4.2
On 08/12/2010 21:22, Jonas Maebe wrote:
On 08 Dec 2010, at 21:32, Martin wrote:
Vincent did some tests with dwarf on win 64 bit.
with the lates (7.2.5) gdb and trunk results are fine = working.
but with fpc 2.4.2 instead there are strange errors:
It simply means that there is an error in
