On 11 Mar 2009, at 15:12, Jonas Maebe wrote:
It may even be quite challenging to generate debug information for
something like that with Stabs. For DWARF, it seems there is some
code that generates debug information in some cases, but only for
var a: type absolute b;-style expressions
And in fact, the same can be done to generate for properties that directly
map to variables/fields. Just one question: what should the debug
information point the debugger to in case of
a) a property without a read specifier, but with a write specifier going
directly to a field? Nothing, or
On 14 Mar 2009, at 09:16, dmitry boyarintsev wrote:
And in fact, the same can be done to generate for properties that
directly
map to variables/fields. Just one question: what should the debug
information point the debugger to in case of
a) a property without a read specifier, but with a
On 14 Mar 2009, at 09:16, dmitry boyarintsev wrote:
writing a property directly in the field is a hack
No, it's guaranteeing future compatibility, because by using a
property you ensure that you can later on replace the setter with a
procedure if necessary, without breaking existing
No, it's guaranteeing future compatibility, because by using a property you
ensure that you can later on replace the setter with a procedure if
necessary, without breaking existing source code (at least in FPC 2.3.1; FPC
2.2.x misses several checks, allowing you to do all sorts of things with
On 14 Mar 2009, at 09:46, dmitry boyarintsev wrote:
No, it's guaranteeing future compatibility, because by using a
property you
ensure that you can later on replace the setter with a procedure if
necessary, without breaking existing source code (at least in FPC
2.3.1; FPC
2.2.x misses
Jonas Maebe schrieb:
On 11 Mar 2009, at 15:12, Jonas Maebe wrote:
It may even be quite challenging to generate debug information for
something like that with Stabs. For DWARF, it seems there is some code
that generates debug information in some cases, but only for var a:
type absolute
On 14 Mar 2009, at 10:42, Florian Klaempfl wrote:
Jonas Maebe schrieb:
It turned out that DWARF2 was enough, so the implementation should
already work with currently released GDB versions (see
http://bugs.freepascal.org/view.php?id=13313 for some caveats).
And in fact, the same can be done
El Sat, 14 Mar 2009 10:42:14 +0100
Florian Klaempfl flor...@freepascal.org escribió:
a) a property without a read specifier, but with a write specifier
going directly to a field? Nothing, or that field?
Nothing. This property is not readable.
It's not readable by the users of the class,
On 14 Mar 2009, at 11:32, Luca Olivetti wrote:
El Sat, 14 Mar 2009 10:42:14 +0100
Florian Klaempfl flor...@freepascal.org escribió:
a) a property without a read specifier, but with a write specifier
going directly to a field? Nothing, or that field?
Nothing. This property is not readable.
On Sat, 14 Mar 2009, Jonas Maebe wrote:
On 14 Mar 2009, at 11:32, Luca Olivetti wrote:
El Sat, 14 Mar 2009 10:42:14 +0100
Florian Klaempfl flor...@freepascal.org escribió:
a) a property without a read specifier, but with a write specifier
going directly to a field? Nothing, or
On 14 Mar 2009, at 11:52, Michael Van Canneyt wrote:
The watches window shows 'Cannot read a write-only property'.
Ok, thanks. Support for DWARF2 debug info for properties with an
accessor that does not pass via a function is committed.
Jonas
On 13 Mar 09, at 20:57, Constantine Cusulos wrote:
.
.
In any case, if anybody has a few pointers on how i could begin a fresh
start, please submit them.
Sorry, I skipped this part yesterday. Considering the fact that
there's at least partial support of OpenBSD in the compiler (there
may
Jonas Maebe wrote:
On 14 Mar 2009, at 11:52, Michael Van Canneyt wrote:
The watches window shows 'Cannot read a write-only property'.
Ok, thanks. Support for DWARF2 debug info for properties with an
accessor that does not pass via a function is committed.
I'm glad to check it but how
On 14 Mar 2009, at 15:00, Paul Ishenin wrote:
Jonas Maebe wrote:
Ok, thanks. Support for DWARF2 debug info for properties with an
accessor that does not pass via a function is committed.
I'm glad to check it but how (fpc r12883)?
c:\programming\fpc\bin\i386-win32\ppc386.exe -O1 -gl
Jonas Maebe wrote:
It's the DWARF version of the lineinfo unit. It's only required to get
line numbers in backtraces when a program crashes. Apparently, it
hasn't been ported to Win32 yet, but it's not required to debug. Just
leave out the -gl parameter.
Ok, I tried to fix it by changing
On 14 Mar 09, at 21:27, Paul Ishenin wrote:
Jonas Maebe wrote:
It's the DWARF version of the lineinfo unit. It's only required to get
line numbers in backtraces when a program crashes. Apparently, it
hasn't been ported to Win32 yet, but it's not required to debug. Just
leave out the
Tomas Hajny wrote:
Keeping -gl instead of -gw?
Sorry, leave out was not in my head dictionary :)
c:\programming\fpc\bin\i386-win32\ppc386.exe -gw test.pp
(gdb) break test.pp:8
invalid dwarf2 offset 4243567
No luck :(
Best regards,
Paul Ishenin.
On 14 Mar 2009, at 15:42, Paul Ishenin wrote:
Tomas Hajny wrote:
Keeping -gl instead of -gw?
Sorry, leave out was not in my head dictionary :)
c:\programming\fpc\bin\i386-win32\ppc386.exe -gw test.pp
(gdb) break test.pp:8
invalid dwarf2 offset 4243567
No luck :(
Strange, that error
Jonas Maebe wrote:
Strange, that error looks very much like the one that should have been
fixed by http://bugs.freepascal.org/view.php?id=12872
Yes.
I tried to compile so (gdb complained the same way):
c:\programming\fpc\bin\i386-win32\ppc386.exe -Aas -gw test.pp
and fpc wrote me this note:
On 14 Mar 2009, at 15:27, Paul Ishenin wrote:
Jonas Maebe wrote:
It's the DWARF version of the lineinfo unit. It's only required to
get line numbers in backtraces when a program crashes. Apparently,
it hasn't been ported to Win32 yet, but it's not required to debug.
Just leave out the
On 14 Mar 2009, at 15:59, Paul Ishenin wrote:
Jonas Maebe wrote:
Strange, that error looks very much like the one that should have
been fixed by http://bugs.freepascal.org/view.php?id=12872
Yes.
I tried to compile so (gdb complained the same way):
On 14 Mar 2009, at 15:59, Paul Ishenin wrote:
Jonas Maebe wrote:
Strange, that error looks very much like the one that should have
been fixed by http://bugs.freepascal.org/view.php?id=12872
Yes.
I tried to compile so (gdb complained the same way):
Hello,
Von: Paul Ishenin webpi...@mail.ru
Jonas Maebe wrote:
It's the DWARF version of the lineinfo unit. It's only required to get
line numbers in backtraces when a program crashes. Apparently, it
hasn't been ported to Win32 yet, but it's not required to debug. Just
leave out the
Op vrijdag 13-03-2009 om 20:29 uur [tijdzone -0700], schreef ABorka:
Can't add notes to resolved reports so I write here instead. :)
If you think that a bug-report is closed while it shoudn't, you can
re-open it and add a note.
I assumed the FCL-web patches/changes I submitted will be applied
25 matches
Mail list logo
