Mail Archives: djgpp-workers/2009/09/08/16:50:45
-----Message d'origine-----
De : Eli Zaretskii [mailto:eliz AT gnu DOT org]
Envoy=E9 : Monday, September 07, 2009 7:53 PM
=C0 : djgpp-workers AT delorie DOT com
Objet : Re: Building latest GDB snapshots
From: "Pierre Muller" <muller AT ics DOT u-strasbg DOT fr>
Date: Mon, 7 Sep 2009 10:36:15 +0200
I tried to hack your djconfig.sh
in order to be able to use it
on the CVS tree directly, but I still
get crashes in the configure stages.
This makes it impossible for me to
test DJGPP gdb.
What are the problems that you need to hack the script? It works for
me unaltered (assuming you are using the version from after I posted
the message to which you respond). What stage(s) crash, and what are
the error messages?
I was trying to use the script with CVS HEAD directly,
but that apparently doesn't work :(
[Cacher les citations]
Btw, I don't build from CVS, I download the latest snapshot from
sourceware.org and build that. That's because the build procedure
(described in gdb/config/djgpp/README) needs to unpack the tarball via
the djunpack.bat batch file, renaming some of the files as it unpacks.
It's hard to do the same automatically if you build out of CVS.
However, the renamed files are those which are not normally used in
compiling the DJGPP port, so I don't see how that could matter.
OK, I tried it your way, and finally got it to complete
a compilation of GDB, great :)
Nevertheless, I first tried to compile in a separate
directory (I wanted to check both 2.03 and 2.04...)
and it crashed when I tried this :(
But directly in source directory your way works !
Could you tell me how you create the zip file?
Sorry, I don't understand: what zip file?
I thought that you were using a gdbXXXsrc.zip as for the DJGPP =20
distributions.
By the way, did you have
the time to look at my dbgcom.c changes
related to multiple watchpoints?
I already discovered one strange thing about the
multiple inferiors support:
Trying to debug gdb with itself,
I restarted gdb several times (as debuggee)
and finally, when I try to quit, I get this:
(top-gdb) q
A debugging session is active.
Inferior 2 [process 42] will be killed.
Inferior 1 [process 42] will be killed.
Quit anyway? (y or n)
The first killed inferior when I restart using 'run' doesn't seem
to be correctly removed.
Pierre
- Raw text -