Mattias Gaertner wrote: > On Thu, 11 Dec 2008 09:39:38 +0100 > svaa <s...@ciberpiula.net> wrote: > >> Hello: >> >> I've decide to use the this work around. I write to filetext and in a >> terminal I use "tail -f <file>". It lets me stop in a breakpoint from >> the IDE and watch in the terminal the current value with a writeln. >> It's not the best, but it works for what I need. May be later I will >> learn how to use the gdb from command line. >> >> By the way, I thought gdb was unable to display Pascal variables, but >> if gdb is able to display the value of any variable in Pascal, what's >> the problem of Lazarus's IDE in displaying the value? It uses gdb as >> debugger backend. doesn't it? > > Yes. But not every variable has a simple mapping in the debugging info. > MSEGui does some more tricks to fill some gaps. > The codetools can probably provide enough information to map. > Marc can probably give more details.
The current debugger should be able to display all variable values (except those defined with absolute and maybe those in procedures defined within procedures) So please let me know in what situation it fails (if gdb is able to show them) Properties are a different beast. Marc _______________________________________________ Lazarus mailing list Lazarus@lazarus.freepascal.org http://www.lazarus.freepascal.org/mailman/listinfo/lazarus
