Re: Problem in debugging GPS

[Martin Krischik <krischik@users.sourceforge.net>]

Ludovic Brenta wrote:

> Martin Krischik <krischik@users.sourceforge.net> writes:
>>> I modified GPS to work with gcc 4.1.1. using gcc 4.1.1
>>
>> Great - I did not get that far. How about joining The GNU Ada
>> Project [1] and share your patches with the rest of us? We alwas
>> welcome new maintainers and if you got the GPS to compile you
>> certainly are our man.
>>
>> Martin
>>
>> [1] http://gnuada.sf.net
> 
> If you like, I can send you my changes.  I've not only added a patch
> to the GPS sources themselves, but I've also rewritten the build
> machinery in a drastically simplistic way, consisting of *one*
> Makefile (the famous debian/rules) and *one* GNAT project file.  This
> comes at the expense of some flexibility; these scripts are designed
> to work on Debian and only on Debian.

But they are probably easier to read the en automake/autoconf stuff.

> I also make heavy use of shared libraries.  My GPS uses not only
> libgtkada.so.2.8.1, but also libtemplates_parser.so.10,
> libgnatvsn.so.4.1, libgnatprj.so.4.1, and libpython2.4.so.1 (yes,
> Python is enabled in the Debian build, even in GPS 2.1.0).  Thus, I
> completely avoid the code duplication that AdaCore seem so fond of.

I never understood that. And am always nagged AdaCore about it. But they
allways mandated that is has to be that way and it would not work any other
way...

Anyway: I would not mind adding similar libs to the R7 distribution (which
is currently not in planning ;-) ).

> The patches, on the other hand, are not specific to Debian, so you
> could try them if you like.  They apply cleanly on the pristine
> sources for GPS 4.0.0, and are managed with quilt.  It is also very
> easy to apply them manually if you just read the short file,
> patches/series.  The patch "gcc-4.1.patch" in which you are interested
> is a mere 269 lines long.

A mere 269 lines....

> The down side is that, as I said, GPS crashes when it opens a "file
> open" dialog.  The problem looks like a stack overflow in GTK+, but
> I'm not sure.  I recompiled with -O0 but got the same results.  -O0
> -fstack-check fared no better.  I still don't know if it's a compiler
> bug or a GPS bug.  Since testgtk works correctly, I don't think it is
> a GtkAda or GTK+ bug.

Up until I deleted my .gkt* and .gnome files any GTK+ application started by
root crashed. Before you ask: vim is gtk+.

For my main user user Gtk+ applications crash when opening a menu. But only
when they where started from an icon. They work fine when started from an
terminal window. ?!?!

And if I start gnome-control-center beforehand the applications look all
different as when I don't.

Mind you I use KDE as desktop. But then: KDE applications never make such a
fuss - even when started under a GNOME desktop. It is just that Gtk/GNOME
is such a "Mimose" as we would say in Germany (Mimose: a flower which dies
quickly when not treated to absolute perfection).

> You can get the Debian scripts and patches from my Monotone server on
> Ada-France, if you want.  The reasons why I did not join the GNU Ada
> project on SourceForge are because (a) I dislike Subversion, (b) the
> Debian patches are older and much more extensive than the ones you
> have, and (c) the build machineries mandated by the package managers
> (RPM vs. DPKG) are radically different; so, merging the Debian patches
> and GNU Ada would be quite a lot of work.  I'm not against it, though.

Ok for (a) and (b) - but for (c): RPM is just one option. The Solaris
maintainer create tar-balls. For MinGW I too have tried tar-balls and I
have created quite a well working RPM-Spec to Tarball-Bash converter. Only
MinGW on its own does not compile at all. Even Arno mentioned once that
AdaCore uses cygwin for automake/autoconf etc.pp. So my current hopes are
on an MinGW/Cygwin combo for MS-Windows.

Martin
-- 
mailto://krischik@users.sourceforge.net
Ada programming at: http://ada.krischik.com