> Given the problems that 3.1.3 seems to be having, it sounds like it > might be worth our while to concentrate on 4.0.0 instead. But since > you're the primary maintainer, that's your call. :-)
Mmh, you're right, they do look like they're the same bug. As I said, 3.1.3 works much better on i386 than 4.0.0 does; it does not have that particular bug, it has other, less critical ones instead. If you would like to experiment with 4.0.0, you need to get my build scripts and patches from my Monotone database. The work is completed, i.e. the scripts and patches produce an executable that reproduces your bug even on i386. You can find full instructions for doing that in the archives of comp.lang.ada for Sept 25, 2006; look at the first message in the thread "ANNOUNCE: Debian build scripts on a public Monotone server". The file gnat-gps_4.0.0.orig.tar.gz is in http://www.ada-france.org/debian/pool. You need to check out the branch "org.debian.gnat-gps" as opposed to "org.debian.gnat-gps.3.1.3". If you manage to patch 4.0.0 to fix that nasty Storage_Error, I will consider switching to that in Debian. In the mean time, 3.1.3 on i386 is a little less buggy. > I'm compiling with a bunch of additional switches now and getting a > bunch of warnings, some of which are very definitely indicative of > this application not being 64-bit clean, such as: [...] Wow, that's disturbing, and it suggests that maybe, switching to 4.0.0 might be worthwhile indeed. Could you try to compile it and see if it produces the same warnings? I seem to remember that AdaCore does have a 64-bit version of GPS somewhere. Maybe they introduced that feature only in 4.0.0. > I made the exception for gvd-canvas.adb in order to get it past the > compiler bug, and for codefix-text_manager.adb because with > '-fstack-check' it would throw the following compiler error: > > codefix-text_manager.adb:2301:45: dynamically tagged expression not > allowed > > I'd like to somehow fix the source so that the "tagged expression" > error doesn't occur with -fstack-check but I don't know how to fix > that type of error just yet. What exactly does it imply in this > context? Easy. $ quilt pop -a # unapply all patches Then, edit the file patches/series. Uncomment the line that mentions patches/dynamically-tagged-expressions.patch. Then: $ quilt push -a # reapply all patches Then you can remove the special case for codefix-text_manager.adb and recompile. (in fact, I made patches/dynamically-tagged-expressions.patch for GPS 4.0.0, but I think it applies cleanly on 3.1.3 as well.) > Finally, I get lots of warnings like this with '-fstack-check': > > /usr/src/Debian/Ada/GPS/3.1.3-3/gnat-gps-3.1.3/gps/src/gps-main.adb:1676: > warning: frame size too large for reliable stack checking > > How can I increase whatever limit it's using to determine that the > frame size is too large? I also saw these warnings but I have no idea how to make them go away. I suggest you run that question on [EMAIL PROTECTED] (family problems at home are sucking my time since Saturday; sorry that I can't help you more. I hope encouragements will help. I'm with you, Kevin :) ) -- Ludovic Brenta. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
