[Lazarus] Class operators

Graeme Geldenhuys graemeg.lists at gmail.com
Thu Sep 8 13:38:10 CEST 2011


On 08/09/2011, Martin wrote:
>
> As i wrote, it takes a bit longer: not sure if it is gdb, or just the
> pipe used to get gdb's output into lazarus. (afaik on win, those pipes
> are slow, haven't speed tested them on linux)

Could be, but I can't say I have really seen pipes being slow under
Linux either. I have a few applications that use pipes to read data
etc.. They all seem quite speedy.


> Menu: "View" > "Debug winows" > "debug output" (I advice to open, it
> before running your app, or it may take several seconds or loner to open

I attached the full output in a archived text file.

I see the following line appear instantly when I hover the mouse over
Sender in the code... Then the delay, then the lots of text output.

   <-data-evaluate-expression TfpgButton(TfpgButton(Sender))^>


> BTW, if you get a hint for the global "Form1" variabl;e => how long does
> that take. It should get the same info.

This took almost double as long to output in the Debug Window. I
thought my IDE froze or something, then as soon as I wanted to kill
Lazarus IDE, I saw the text dump in the Debug Output window. I include
that output in the attached archive too.


> BTW: if you got time => try running ./debugger/test/GDBMI/TestGDBMI.lpi
> I would be interested, how well it does on 64 bit linux. (if there are
> error, you can enable "write logs" and send them (fro the failed tests)
> -- though the xml output already contains basic info.

There seems to be lots of failures. I'll send you the xml and log
files in a private message. It's too big to attach in a mailing list
message.


> then especially if they are classes, record, arrays (arrays aren't to
> well handled yet, just another gdb limit :(  )

I'm working on that - though slower than I was hoping. I'm busy
implementing a Object Pascal based debugger for FPC (a fork of duby
with lots of code cleanup). Only reading the DWARF debug information
that FPC outputs (I'm not interested in STABS). I'm a totally newbie
when it comes to debuggers, so I had to do a lot of background reading
before I could start. If I have something worth showing, I'll make the
project public. Hopefully somebody like yourself, with good debugger
experience or DWARF knowledge, will then be able to give me some
pointers.

Just the other day I had to do some maintenance work on a old Delphi 7
project. I forgot how wonderful Delphi's debugging was! I didn't need
to write a single log file or console output. The built-in IDE
debugger just worked perfectly.  It's loooooong over due that FPC has
something similar. One cannot have a compiler without a debugger!


-- 
Regards,
  - Graeme -


_______________________________________________
fpGUI - a cross-platform Free Pascal GUI toolkit
http://fpgui.sourceforge.net
-------------- next part --------------
A non-text attachment was scrubbed...
Name: debug_output.tar.gz
Type: application/x-gzip
Size: 8300 bytes
Desc: not available
URL: <http://lists.lazarus-ide.org/pipermail/lazarus/attachments/20110908/7b16ff21/attachment-0003.bin>


More information about the Lazarus mailing list