On Sunday 17 October 2010 01:54:00 Joost van der Sluis wrote:
I also work on a 64 but system. You're sure you used fpc 2.5.1? And that
you disabled smart-linking?
I used attached program to test gdb. (place breakpoint at second
position and do a 'p s[2]')
Form command line it works as
On Sun, 2010-10-17 at 14:52 +0300, Juha Manninen (gmail) wrote:
On Sunday 17 October 2010 01:54:00 Joost van der Sluis wrote:
I also work on a 64 but system. You're sure you used fpc 2.5.1? And
that
you disabled smart-linking?
What's up with all the empty lines in your mail?
I used
On Sunday 17 October 2010 13:32:19 Joost van der Sluis wrote:
What's up with all the empty lines in your mail?
?
I don't see many empty lines.
Form command line it works as advertized!
No, it does not. It should show 'test'#0'string'. At least with Dwarf-3.
arrays.pas, built with -gw,
17.10.2010 18:20, Juha Manninen (gmail) пишет:
...
Can you correct your time please?
--
Best regards,
Maxim Ganetsky mailto:gan...@narod.ru
--
___
Lazarus mailing list
Lazarus@lists.lazarus.freepascal.org
On Sunday 17 October 2010 16:29:57 Maxim Ganetsky wrote:
Can you correct your time please?
Ok, I fixed it now. This mail should have a correct time stamp. I don't know
why it happens but dual-booting to Windows Vista always messes the time.
There are some youngsters who use this super-computer
17.10.2010 20:01, Juha Manninen (gmail) пишет:
On Sunday 17 October 2010 16:29:57 Maxim Ganetsky wrote:
Can you correct your time please?
Ok, I fixed it now. This mail should have a correct time stamp. I don't know
why it happens but dual-booting to Windows Vista always messes the time.
There
Juha Manninen (gmail) schrieb:
On Sunday 17 October 2010 16:29:57 Maxim Ganetsky wrote:
Can you correct your time please?
Ok, I fixed it now. This mail should have a correct time stamp. I don't know
why it happens but dual-booting to Windows Vista always messes the time.
I also had and
On Wed, 2010-10-13 at 15:08 +0200, Martin Schreiber wrote:
Graeme Geldenhuys wrote:
It's just amazing that everybody known that the debugger support in
Lazarus and FPC absolutely sucks! Even the crappy Kylix 3 has better
debugger support.
I think you are wrong. I recently had to debug
On Wed, 2010-10-13 at 15:15 +0200, Graeme Geldenhuys wrote:
Op 2010-10-13 14:43, Michael Van Canneyt het geskryf:
Why do you say it sucks ?
Simply for a lack of a stronger word. I was holding back on my frustrations.
It works, kind of. It depends on your expectations.
My
Joost van der Sluis kirjoitti lauantai, 16. lokakuuta 2010 18:15:40:
Ah, now I see what you're problem is. You're trying to access
indexed-strings. I've spend quite some time fixing that. It works now if
you use Dwarf-3, fpc 2.5.1 and Fedora 13.
So if you really can't do without, just switch
On Sat, 2010-10-16 at 19:52 +0300, Juha Manninen wrote:
Joost van der Sluis kirjoitti lauantai, 16. lokakuuta 2010 18:15:40:
Ah, now I see what you're problem is. You're trying to access
indexed-strings. I've spend quite some time fixing that. It works now if
you use Dwarf-3, fpc 2.5.1 and
Le 16/10/2010 17:15, Joost van der Sluis a écrit :
Ah, now I see what you're problem is. You're trying to access
indexed-strings. I've spend quite some time fixing that. It works now if
you use Dwarf-3, fpc 2.5.1 and Fedora 13.
So if you really can't do without, just switch to Fedora and
On Saturday 16 October 2010 19:56:28 Joost van der Sluis wrote:
So if you really can't do without, just switch to Fedora and you're
done. ;)
Wow!
How to generate Dwarf-3 debug info?
-gw3
I updated the latest FPC trunk version.
From a simple test program I get:
On Sat, 2010-10-16 at 21:36 +0200, Thierry B. wrote:
Le 16/10/2010 17:15, Joost van der Sluis a écrit :
Ah, now I see what you're problem is. You're trying to access
indexed-strings. I've spend quite some time fixing that. It works now if
you use Dwarf-3, fpc 2.5.1 and Fedora 13.
So
On Sun, 2010-10-17 at 00:37 +0300, Juha Manninen (gmail) wrote:
On Saturday 16 October 2010 19:56:28 Joost van der Sluis wrote:
So if you really can't do without, just switch to Fedora and you're
done. ;)
Wow!
How to generate Dwarf-3 debug info?
-gw3
I updated the latest
On Thu, 14 Oct 2010, Adem wrote:
On 2010-10-13 10:25, Graeme Geldenhuys wrote:
Such basic features really should work in any IDE. If we can't trust the
debugger, who can we trust?
I don't mean to hijack this thread but as we're talking about debugging here,
there's a question I have been
Hi,
http://mantis.freepascal.org/view.php?id=17619
I can reproduce this on two very different machines (32 bit laptop running
Ubuntu 8.04.4, and a 64-bit desktop running Ubuntu 10.04.1). I'm using FPC
2.4.3 and latest SVN Lazarus.
Such basic features really should work in any IDE. If we can't
2010/10/13 Graeme Geldenhuys graemeg.li...@gmail.com:
Such basic features really should work in any IDE. If we can't trust the
debugger, who can we trust?
But in fact they really don't work in complex cases as indexed string
expression evaluation.
You can not trust a debugger. You can trust
On 13 October 2010 12:57, Vincent Snijders wrote:
But in fact they really don't work in complex cases as indexed string
expression evaluation.
Huh? Are you saying that rather simple code example is actually complex?
You can not trust a debugger. You can trust output to the console instead.
13.10.2010 19:20, Graeme Geldenhuys wrote:
Just in your world (or is that FPC and Lazarus's world) that it true.
Everybody else in every other programming language uses the debugger
output as correct - for debugging purposes none the less.
I guess yet another example of why a native Object
On 13 October 2010 08:25, Graeme Geldenhuys graemeg.li...@gmail.com wrote:
--8--
debugger, who can we trust?
Well, that depends on how well you deal with disappointment ;)
--
___
Lazarus mailing list
Lazarus@lists.lazarus.freepascal.org
Op 2010-10-13 13:42, Paul Ishenin het geskryf:
are open. We just need someone who will work on debugger support at
least 10-15 hours per week. Those parts of lazarus on which someone
constantly invest time (like source editor or codetools) are good (even
compared to commercial products).
Am 13.10.2010 14:31, schrieb Graeme Geldenhuys:
It's just amazing that everybody known that the debugger support in Lazarus
and FPC absolutely sucks! Even the crappy Kylix 3 has better debugger
support. Yet those developers that have spare time will rather spend there
time with more IDE
On Wed, 13 Oct 2010, Graeme Geldenhuys wrote:
Op 2010-10-13 13:42, Paul Ishenin het geskryf:
are open. We just need someone who will work on debugger support at
least 10-15 hours per week. Those parts of lazarus on which someone
constantly invest time (like source editor or codetools) are
Op 2010-10-13 13:51, Michael Van Canneyt het geskryf:
Comparing it to the Borland debugger which is in it's roots 25 years old,
I explicitly compared it with Kylix, which was probably the crappiest
product Borland released in its existence. Yet it still leaves the
FPC+Lazarus solution in the
On Wed, 13 Oct 2010, Graeme Geldenhuys wrote:
Op 2010-10-13 13:51, Michael Van Canneyt het geskryf:
Comparing it to the Borland debugger which is in it's roots 25 years old,
I explicitly compared it with Kylix, which was probably the crappiest
product Borland released in its existence. Yet
Graeme Geldenhuys wrote:
It's just amazing that everybody known that the debugger support in
Lazarus and FPC absolutely sucks! Even the crappy Kylix 3 has better
debugger support.
I think you are wrong. I recently had to debug an old project with Delphi 7.
Argh! No possibility to explore
Op 2010-10-13 14:43, Michael Van Canneyt het geskryf:
Why do you say it sucks ?
Simply for a lack of a stronger word. I was holding back on my frustrations.
It works, kind of. It depends on your expectations.
My expectations are rather low at the moment. Just show me the f**ken value
of
Graeme Geldenhuys wrote:
So how did I come across this lovely debugging screwup...? I was trying to
write a string parser, so debugging actual character values are a rather
big deal in a string parser. But unfortunately Lazarus was NO help at all.
You should not use character indices with
Op 2010-10-13 15:08, Martin Schreiber het geskryf:
based, sometimes it is necessary to store a value into a testvariable but
Oh, I tried this nugget you shared with me a little while back, but
unfortunately as my screenshots show, that helped absolutely zero in this
case. Watches debug window
Op 2010-10-13 15:18, Martin Schreiber het geskryf:
You should not use character indices with utf-8 anyway. ;-)
The string parser I am writing doesn't accept Unicode text. There are only
30 or so keywords in plain ASCII text, so inspecting the first character
via an index is perfectly legal in
On Wed, 13 Oct 2010, Graeme Geldenhuys wrote:
Op 2010-10-13 14:43, Michael Van Canneyt het geskryf:
Why do you say it sucks ?
Simply for a lack of a stronger word. I was holding back on my frustrations.
That you are frustrated is obvious to all, I would say =-)
It works, kind of. It
On 13 October 2010 15:25, Michael Van Canneyt wrote:
That you are frustrated is obvious to all, I would say =-)
:) My apologies... I'll go drink a coffee on the deck to relax a bit.
If I ever need to see actual values, I send them with SendDebug() to the
debug server window, for the simple
On Wed, 13 Oct 2010, Graeme Geldenhuys wrote:
On 13 October 2010 15:25, Michael Van Canneyt wrote:
That you are frustrated is obvious to all, I would say =-)
:) My apologies... I'll go drink a coffee on the deck to relax a bit.
Nono, coffee is bad for your nerves. Drink a beer instead
13.10.2010 20:31, Graeme Geldenhuys wrote:
It's just amazing that everybody known that the debugger support in
Lazarus
and FPC absolutely sucks! Even the crappy Kylix 3 has better debugger
support. Yet those developers that have spare time will rather spend there
time with more IDE eye-candy
Op 2010-10-13 15:33, Michael Van Canneyt het geskryf:
Ah, this might be the solution then. Thanks for that.
You're welcome. Note that this uses
- dbugintf unit from FCL
- debugserver tool (lazarus/tools/debugserver)
I did a few quick tests using various data types and even property values
On 13/10/2010 14:15, Graeme Geldenhuys wrote:
So now I'm really confused at the what to believe in the Lazarus IDE?
Tooltips that show values, but the wrong values, or the Watches debug
window that shows nothing. And yes, both watches are Enabled.
maybe you attach the debug output window
2010/10/13 Graeme Geldenhuys graemeg.li...@gmail.com
On 13 October 2010 12:57, Vincent Snijders wrote:
But in fact they really don't work in complex cases as indexed string
expression evaluation.
Huh? Are you saying that rather simple code example is actually complex?
You can not
On Wed, 13 Oct 2010, Graeme Geldenhuys wrote:
Op 2010-10-13 15:33, Michael Van Canneyt het geskryf:
Ah, this might be the solution then. Thanks for that.
You're welcome. Note that this uses
- dbugintf unit from FCL
- debugserver tool (lazarus/tools/debugserver)
I did a few quick tests
Op 2010-10-13 16:11, Martin het geskryf:
maybe you attach the debug output window content?
So someone can look into why the watches did not show anything...
FPC: 2.4.3
System: Ubuntu Linux 10.04.1 64-bit
Lazarus: latest svn
The local char variable is: testvar
-[ debug
2010/10/13 Frank Church vfcli...@gmail.com:
I posted this article - Observations on FreePascal and Lazarus Development
on my blog a few days ago, but because I haven't started any concrete work
I added the blog to:
On 13 October 2010 15:35, Vincent Snijders vincent.snijd...@gmail.comwrote:
2010/10/13 Frank Church vfcli...@gmail.com:
I posted this article - Observations on FreePascal and Lazarus
Development
on my blog a few days ago, but because I haven't started any concrete
work
I added the blog
Op 2010-10-13 16:12, Frank Church het geskryf:
@Graeme: I have to say that sometimes you make pointed criticisms which
rub people the wrong way.
Funny that, my wife (of all people) accused me of the same thing last week.
Maybe it's just the way I write emails, but it's not always intended to
On Wed, Oct 13, 2010 at 2:31 PM, Graeme Geldenhuys
graemeg.li...@gmail.com wrote:
It's just amazing that everybody known that the debugger support in Lazarus
and FPC absolutely sucks!
I don't think it sucks. It's better then vi, devcpp, doctor java, eclipse, etc.
In general, GDB is not at all
On Wed, 13 Oct 2010 14:53:01 +0200
Graeme Geldenhuys graemeg.li...@gmail.com wrote:
I would have thought everybody working with
a compiler (that's any type of software developer) would know that a
compiler and debugger go hand-in-hand.
That's more or less true but working with different
2010/10/13 Felipe Monteiro de Carvalho felipemonteiro.carva...@gmail.com:
Plus, the tooltips always work for me. Maybe because I very rarely use
the data type Char.
I don't the problem is not the data type char, but that somewhere in
the debugger tool chain (from lazarus tool-tips front end to
On Wed, 13 Oct 2010, Vincent Snijders wrote:
2010/10/13 Felipe Monteiro de Carvalho felipemonteiro.carva...@gmail.com:
Plus, the tooltips always work for me. Maybe because I very rarely use
the data type Char.
I don't the problem is not the data type char, but that somewhere in
the
On 13/10/2010 18:08, Michael Van Canneyt wrote:
I don't the problem is not the data type char, but that somewhere in
the debugger tool chain (from lazarus tool-tips front end to the gdb
backend using the fpc generated debug info) the assumption is used
that pascal strings are indexed starting
On 13 October 2010 19:26, Martin laza...@mfriebe.de wrote:
actually, I think in dwarf 3 the lower bound can be defined (and from a
search in fpc sources, it may even be done...); but I couldn't get dwarf 3
results to work at all...
Probably the wrong list to ask, but what is the state of
On 13 October 2010 18:32, Reimar Grabowski wrote:
Once you found these ways the quality of the debugger gets less important
as the debugger sees less use.
And that to me seems like the wrong way of approaching the problem.
Treat the cause of the problem, not (band-aid) the symptoms. The
2010/10/13 Graeme Geldenhuys graemeg.li...@gmail.com:
On 13 October 2010 18:32, Reimar Grabowski wrote:
Once you found these ways the quality of the debugger gets less important
as the debugger sees less use.
And that to me seems like the wrong way of approaching the problem.
Treat the
On 2010-10-13 10:25, Graeme Geldenhuys wrote:
Such basic features really should work in any IDE. If we can't trust the
debugger, who can we trust?
I don't mean to hijack this thread but as we're talking about debugging
here, there's a question I have been meaning to ask on the subject:
52 matches
Mail list logo
