Re: [Vala] Debugging

[Brian Duffy <brduffy gmail com>]

My compiler arguments have always been -g --pkg clutter-1.0 --save-temps ...

Actually, I just set a break point in my code and tried to inspect the
property value of a clutter object that had been instantiated. It seems
that gdb can't read the value of this property at the vala code page level.
It can however read the values of variables that I have defined in vala
itself (such as a loop counter variables). Someone on stackoverflow
recommended I use clutter_actor_get_width(r) where "r" is the name of the
clutter Rectangle that had been instantiated. I typed that into the
immediate window in monodevelop (using gdb debugger) and that returned my
value. I still have not gotten an answer I can understand as to why I can't
read property values of clutter objects when I break in my vala code
without calling a clutter function. I can print the value out with printf
and look at it in the external console but I can't evaluate the value with
the debugger. Strange, but thanks for the feedback.

b



On Sat, Dec 17, 2011 at 5:23 AM, Luca Bruno <lethalman88 gmail com> wrote:

> On Sat, Dec 17, 2011 at 4:56 AM, PCMan <pcman tw gmail com> wrote:
>
> > I believe that he is talking about reading generated C code during
> > debugging.
> > When there is a crash, gdb listed generated C code rather than vala
> source.
> > As everyone knows, the C code generated by vala is not quite readable and
> > contains quite a lot of temporary variables, which makes debugging
> annoying
> > sometimes.
>
> Then use valac -g.
>
> --
> www.debian.org - The Universal Operating System
>
> _______________________________________________
> vala-list mailing list
> vala-list gnome org
> http://mail.gnome.org/mailman/listinfo/vala-list


-- 
Duff