[gvd-users] A few questions about gvd

[Arnaud Charlet]

You are subscribed (otherwise you would have received a message telling you
that your post is on hold, waiting for approval).

> It seems that gvd slowly leaks memory on w2k.  If I remember rightly, the
> gvd developers thought this was a gtk+ problem (freeciv used to have the
> same problem, and it also uses gtk+).  Has anyone else noticed this?  Is it
> fixed in newer versions of gtk (as far as I know, it is no longer a problem
> in freeciv, although I haven't tried it for some time)?  Or will gvd be
> moved over to gtk 2.0 at some point?

GVD (under one form or another, posibly GPS) will be moved to 2.0 at some
point, will may indeed solve the problem.

You may also want to rebuild GVD with a newer version of Gtk+ 1.3, although this
is not a trivial task. We have no plans for upgrading the version of Gtk+
used to build GVD 1.2.x

> Is there any way to change the size of the tabs in the source view?  Deeply
> indented C code runs out of the window at 8 spaces per tab.

If I rmeember well, there's a constant in the source code that would allow
to change this setting, but there's apparently no preference or user level
settings for that, so you would need to rebuild GVD.

> The explorer window shows all my C files, along with C files for all the
> library routines that are included in the project - is there anyway to avoid
> them being shown?  Choosing "Delete Files Not Found" does not work - it
> simply removes all the files.  In the "h files" sub-tree, all my headers and
> all the library headers are shown, and they are each shown several times
> (once for each time they are included in a C file somewhere).  Is there
> someway to avoid this?  Do other people get the same effects?  Perhaps there
> is something I could change in my linker options to avoid this?  (I'm using
> a patched cross-compiler version of gcc-2.95.3).

All GVD does is display the result of the gdb command "info sources",
so if you have duplicates, this is because the debug info contains "duplicate"
sources, which may not actually be duplicates (e.g. same source file, but
with different source). Also, I suspect depending on your source search
path settings, different relative paths may account for this difference.
Probably something that can be improved in your build procedures.

Arno