Re: [Lazarus] debug hints in lazarus [Re: [fpc-devel] Status and ideas about debug info (stabs, dwarf / dwar3)]

2011-09-15 Thread Joost van der Sluis
On Tue, 2011-09-13 at 23:28 +0200, Graeme Geldenhuys wrote: On 13 September 2011 22:18, Joost van der Sluis wrote: Funny how experiences can differ. I honestly can't think how anybody can say Lazarus debugging is better than Delphi (or even Kylix 3 from years ago). But as you said, each

Re: [Lazarus] debug hints in lazarus [Re: [fpc-devel] Status and ideas about debug info (stabs, dwarf / dwar3)]

2011-09-15 Thread Martin
On 15/09/2011 18:00, Joost van der Sluis wrote: On Tue, 2011-09-13 at 23:28 +0200, Graeme Geldenhuys wrote: better than with Delphi. That's because when you're debugging on Delphi, the IDE is scaled down to the feature-level of Notepad. Normal code navigation (Ctrl+Click) in Delphi 7 [only

Re: [Lazarus] debug hints in lazarus [Re: [fpc-devel] Status and ideas about debug info (stabs, dwarf / dwar3)]

2011-09-15 Thread Rich Saunders
On 9/15/11 1:21 PM, Martin wrote: That means the way they implemented their feature is extremely inconsistent: 1) in Delphi you are not supposed to edit source wile debugging 2) If inserting lines, in source while debugging (like in Lazarus) Delphi keeps track of line positions, so the

Re: [Lazarus] debug hints in lazarus [Re: [fpc-devel] Status and ideas about debug info (stabs, dwarf / dwar3)]

2011-09-15 Thread Graeme Geldenhuys
On 15 September 2011 19:21, Martin wrote: 1) in Delphi you are not supposed to edit source wile debugging I believe that is their theory, because even in Delphi 7 there is a option to make all edit buffers read-only when debugging is started. -- Regards,   - Graeme -

Re: [Lazarus] debug hints in lazarus [Re: [fpc-devel] Status and ideas about debug info (stabs, dwarf / dwar3)]

2011-09-14 Thread Graeme Geldenhuys
On 13/09/2011 23:34, Martin wrote: And there was no other key shortcut they could have used? I guess not. ;-) Ctrl-F7 or context menu: Debug = evaluate look at the bottom of the window, for giving it a new value. Cool, thanks for the info. And for another way to see an entire object

Re: [Lazarus] debug hints in lazarus [Re: [fpc-devel] Status and ideas about debug info (stabs, dwarf / dwar3)]

2011-09-13 Thread Graeme Geldenhuys
On 13/09/2011 00:12, Martin wrote: I do not recall having ever had an issue with globals, nor local vars. Nope, the problem is still there... just as when I tested it back in 2008-2009. http://opensoft.homeip.net:8080/~graemeg/gdb_issues_with_fpc.png This exact same code works perfectly

Re: [Lazarus] debug hints in lazarus [Re: [fpc-devel] Status and ideas about debug info (stabs, dwarf / dwar3)]

2011-09-13 Thread Joost van der Sluis
On Tue, 2011-09-13 at 14:07 +0200, Graeme Geldenhuys wrote: On 13/09/2011 00:12, Martin wrote: I do not recall having ever had an issue with globals, nor local vars. Nope, the problem is still there... just as when I tested it back in 2008-2009.

Re: [Lazarus] debug hints in lazarus [Re: [fpc-devel] Status and ideas about debug info (stabs, dwarf / dwar3)]

2011-09-13 Thread Martin
On 13/09/2011 13:07, Graeme Geldenhuys wrote: On 13/09/2011 00:12, Martin wrote: I do not recall having ever had an issue with globals, nor local vars. Nope, the problem is still there... just as when I tested it back in 2008-2009.

Re: [Lazarus] debug hints in lazarus [Re: [fpc-devel] Status and ideas about debug info (stabs, dwarf / dwar3)]

2011-09-13 Thread Martin
On 13/09/2011 14:01, Joost van der Sluis wrote: On Tue, 2011-09-13 at 14:07 +0200, Graeme Geldenhuys wrote: On 13/09/2011 00:12, Martin wrote: I do not recall having ever had an issue with globals, nor local vars. Nope, the problem is still there... just as when I tested it back in

Re: [Lazarus] debug hints in lazarus [Re: [fpc-devel] Status and ideas about debug info (stabs, dwarf / dwar3)]

2011-09-13 Thread Joost van der Sluis
On Tue, 2011-09-13 at 15:41 +0100, Martin wrote: On 13/09/2011 14:01, Joost van der Sluis wrote: On Tue, 2011-09-13 at 14:07 +0200, Graeme Geldenhuys wrote: BTW: is it correct that some info about classes from units without debug info, does get into the app? At least if you have an

Re: [Lazarus] debug hints in lazarus [Re: [fpc-devel] Status and ideas about debug info (stabs, dwarf / dwar3)]

2011-09-13 Thread Martin Schreiber
Am 13.09.2011 15:26, schrieb Martin: Given that there seems no alternative to gdb yet, and given that your code can under no circumstances be debugged using gdb = I must say, I have a huge amount of respect for your archivment of implementing fpgui without using any debugging at all. WOW. (scnr

Re: [Lazarus] debug hints in lazarus [Re: [fpc-devel] Status and ideas about debug info (stabs, dwarf / dwar3)]

2011-09-13 Thread Vincent Snijders
An rtl with debug info has advantages such as visibility of global variables. The disadvantage is that step into also steps into compiler helpers, like increasing the reference count of an ansistring or setting up an exception frame. That is the reason, I distribute the RTL for win32 now without

Re: [Lazarus] debug hints in lazarus [Re: [fpc-devel] Status and ideas about debug info (stabs, dwarf / dwar3)]

2011-09-13 Thread Martin
On 13/09/2011 15:49, Joost van der Sluis wrote: On Tue, 2011-09-13 at 15:41 +0100, Martin wrote: On 13/09/2011 14:01, Joost van der Sluis wrote: On Tue, 2011-09-13 at 14:07 +0200, Graeme Geldenhuys wrote: BTW: is it correct that some info about classes from units without debug info, does get

Re: [Lazarus] debug hints in lazarus [Re: [fpc-devel] Status and ideas about debug info (stabs, dwarf / dwar3)]

2011-09-13 Thread Joost van der Sluis
On Tue, 2011-09-13 at 17:10 +0200, Vincent Snijders wrote: An rtl with debug info has advantages such as visibility of global variables. The disadvantage is that step into also steps into compiler helpers, like increasing the reference count of an ansistring or setting up an exception frame.

Re: [Lazarus] debug hints in lazarus [Re: [fpc-devel] Status and ideas about debug info (stabs, dwarf / dwar3)]

2011-09-13 Thread Graeme Geldenhuys
On 13 September 2011 16:26, Martin wrote: ShortDateFormat is declared in the RTL So you need an rtl with debug info. I realized that as soon as I read Vincents reply. :-) But then, why does it work in Delphi? I am using Delphi 7, and there is a separate DEBUG RTL directory, which I am not

Re: [Lazarus] debug hints in lazarus [Re: [fpc-devel] Status and ideas about debug info (stabs, dwarf / dwar3)]

2011-09-13 Thread Martin
On 13/09/2011 19:17, Graeme Geldenhuys wrote: On 13 September 2011 16:26, Martin wrote: ShortDateFormat is declared in the RTL So you need an rtl with debug info. I realized that as soon as I read Vincents reply. :-) But then, why does it work in Delphi? Becuase the delphi compiler (not

Re: [Lazarus] debug hints in lazarus [Re: [fpc-devel] Status and ideas about debug info (stabs, dwarf / dwar3)]

2011-09-13 Thread Sven Barth
On 13.09.2011 14:07, Graeme Geldenhuys wrote: And yes the inspecting properties could change data is a moot point. Delphi allows it, and NOBODY complains about the possible data change issue. The pros far outweigh the cons. We are programmers, we should know what is dangerous or not - but it

Re: [Lazarus] debug hints in lazarus [Re: [fpc-devel] Status and ideas about debug info (stabs, dwarf / dwar3)]

2011-09-13 Thread Graeme Geldenhuys
On 13 September 2011 20:50, Martin wrote: Becuase the delphi compiler (not debugger)  does add infor for the those global vars (but skips any debug info for funtionx)... Ah, sneaky. If it is a plain function (not a method), and if it takes no param = try (without the quotes)

Re: [Lazarus] debug hints in lazarus [Re: [fpc-devel] Status and ideas about debug info (stabs, dwarf / dwar3)]

2011-09-13 Thread Michael Van Canneyt
On Tue, 13 Sep 2011, Sven Barth wrote: On 13.09.2011 14:07, Graeme Geldenhuys wrote: And yes the inspecting properties could change data is a moot point. Delphi allows it, and NOBODY complains about the possible data change issue. The pros far outweigh the cons. We are programmers, we should

Re: [Lazarus] debug hints in lazarus [Re: [fpc-devel] Status and ideas about debug info (stabs, dwarf / dwar3)]

2011-09-13 Thread Martin
On 13/09/2011 20:31, Graeme Geldenhuys wrote: The Watch List window is rather broken as far as I'm concerned. http://bugs.freepascal.org/view.php?id=20230 http://bugs.freepascal.org/view.php?id=18380 http://bugs.freepascal.org/view.php?id=18379 http://bugs.freepascal.org/view.php?id=18035

Re: [Lazarus] debug hints in lazarus [Re: [fpc-devel] Status and ideas about debug info (stabs, dwarf / dwar3)]

2011-09-13 Thread ABorka
...snip... Because I use the watch window. I display: . And the output looks quite good as well The Watch List window is rather broken as far as I'm concerned. http://bugs.freepascal.org/view.php?id=20230 http://bugs.freepascal.org/view.php?id=18380

Re: [Lazarus] debug hints in lazarus [Re: [fpc-devel] Status and ideas about debug info (stabs, dwarf / dwar3)]

2011-09-13 Thread Graeme Geldenhuys
On 13 September 2011 22:18, Joost van der Sluis wrote: Funny how experiences can differ. I honestly can't think how anybody can say Lazarus debugging is better than Delphi (or even Kylix 3 from years ago). But as you said, each persons mileage my vary. :-) better than with Delphi. That's

Re: [Lazarus] debug hints in lazarus [Re: [fpc-devel] Status and ideas about debug info (stabs, dwarf / dwar3)]

2011-09-13 Thread Martin
On 13/09/2011 22:28, Graeme Geldenhuys wrote: better than with Delphi. That's because when you're debugging on Delphi, the IDE is scaled down to the feature-level of Notepad. Normal code navigation (Ctrl+Click) in Delphi 7 [only Delphi I currently have available] is indeed disabled while

[Lazarus] debug hints in lazarus [Re: [fpc-devel] Status and ideas about debug info (stabs, dwarf / dwar3)]

2011-09-12 Thread Martin
cced to lazarus list. please switch list. On 12/09/2011 21:28, Hans-Peter Diettrich wrote: Martin schrieb: Mind, I do NOT want to play down say that the lack of property support. I didn't notice until now that my problems may be related to properties. AFAIR I also couldn't inspect global