Date: Sun, 16 May 1999 07:15:06 +0300 (IDT) From: Eli Zaretskii X-Sender: eliz AT is To: Robert Hoehne cc: djgpp-workers AT delorie DOT com Subject: Re: gdb 4.18 for DJGPP (alpha) In-Reply-To: <3737E4BB.98DFC34A@gmx.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Reply-To: djgpp-workers AT delorie DOT com X-Mailing-List: djgpp-workers AT delorie DOT com X-Unsubscribes-To: listserv AT delorie DOT com Precedence: bulk On Tue, 11 May 1999, Robert Hoehne wrote: > after a very long time it is now ready. I uploaded > to DJ's site the ported gdb 4.18 archives and he placed > them in v2gnu/alphas. Thanks for releasing this! Some problems I had working with this port: With this version, I still get the annoying message when I quit GDB after exiting Emacs that was run under the debugger: warning: cannot close "e:/src/gnu/emacs/emacs": Bad file descriptor (EBADF) This message doesn't get printed if I quit GDB *before* exiting Emacs. Please tell me how can I help you to try to track down this elusive bug. Another problem is that when I restart the program (with `r'), GDB asks whether I indeed want to restart it. If the program has switched stdin to binary mode, the machine is wedged at this point. The same happens if I try to quit the debugger before program termination, when it asks for confirmation. Does GDB use termios in the ported readline? If so, I think if you rebuild GDB with the current library sources from DJ's CVS repository, this problem will go away (the stock v2.02 version didn't redirect buffered stdio functions like getc to the termios hook, and I think GDB uses getc when it asks for Y or N). An alternative solution is to momentarily switch stdin to text mode, and switch it back to the original mode once the user responds with `y' or `n'. I believe GDB already does that elsewhere (e.g., when the `bt' command needs to print more than a single screen-full). Some comments about the binary distribution: - I think that including everything that is produced during the build is a very good idea, since building things from sources is not for the faint of heart. Perhaps libgdb.a (the one you use to build RHIDE) should also be included, if it's not too much trouble to build it. - The file NEWS should be included (README.DJGPP even refers to it). - I think at least the main DJGPP-specific changes relative to the last DJGPP port (4.16) should also be mentioned, because NEWS will not describe them. - I think it's best to distribute man pages already formatted (and thus in man/cat[1-9], not in man/man[1-9]). Otherwise, people would need to install Groff, which is quite a large distribution, just to read the man pages. - The files README and gdb/README seem to be not useful in this case, they mostly talk about building GDB, so they might confuse somebody. - Perhaps README.DJGPP should tell how to update info/DIR, either by running install-info or by editing DIR. I think most people won't know how to do that (or even that they need to do it), and without updating DIR they won't be able to get to the docs from the main menu.