unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Stefan Monnier" <monnier+gnu/emacs@rum.cs.yale.edu>
Cc: monnier+gnu/emacs@rum.cs.yale.edu
Subject: Re: gdb-ui almosts works in NT
Date: Wed, 02 Apr 2003 09:14:34 -0500	[thread overview]
Message-ID: <200304021414.h32EEY6Y025552@rum.cs.yale.edu> (raw)
In-Reply-To: 7263-Wed02Apr2003061204+0300-eliz@elta.co.il

> > From: "Stefan Monnier" <monnier+gnu/emacs@rum.cs.yale.edu>
> > Date: Tue, 01 Apr 2003 16:31:35 -0500
> > > 
> > > 1) gdb-ui doesn't output to the I/O buffer in NT.
> > 
> > Are you sure this is the always the case ?
> > I think it does not depend on gdb-ui but on the underlying gdb session,
> > so it might depend on which gdb executable you're using (native port,
> > mingw, cygwin, dos, godknowswhatelse, ...) and on what kind of runtime
> > library is used by the debugged program (again, native, cygwin,
> > djgpp, ...).
> 
> Just FYI: the DOS port uses only the DJGPP library and runtime, there
> is no other DOS configuration of Emacs that one can build, not for
> years.
> 
> As for Cygwin, this problem might indeed not happen there (and then
> again it might), but the clause suggested by Nick didn't include the
> `cygwin' configuration, so I think it's safe.  Someone who has the
> Cygwin build handy should try this and tell what they found; until
> then, I think we should assume it's Unix-like.

But aren't we talking about different things.
I was talking about how gdb and the debugged program were built,
whereas you're talking about how Emacs is built.  Aren't those
two aspects somewhat orthogonal ?  Can't I run a cygwin gdb within
NTemacs ?
I think a better solution would be to make the creation and/or display
of the I/O buffer conditional on the presence of output.
Or something like that.


	Stefan

  reply	other threads:[~2003-04-02 14:14 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-31 21:04 gdb-ui almosts works in NT Nick Roberts
2003-04-01  4:28 ` Eli Zaretskii
2003-04-01 18:55   ` Edward O'Connor
2003-04-01 21:06     ` Nick Roberts
2003-04-01 21:31       ` Stefan Monnier
2003-04-02  4:12         ` Eli Zaretskii
2003-04-02 14:14           ` Stefan Monnier [this message]
2003-04-03  3:49             ` Eli Zaretskii
2003-04-03  7:55               ` Jason Rumney
2003-04-02  4:08       ` Eli Zaretskii
2003-04-02 17:28   ` Jonathan Luntz
  -- strict thread matches above, loose matches on Subject: below --
2003-04-03 17:29 Nick Roberts
2003-04-03 17:52 ` Jonathan Luntz
     [not found] <3E84A28A.2090407@umich.edu>
2003-03-31  6:45 ` Eli Zaretskii
2003-03-31 15:29   ` Stefan Monnier
2003-03-31 16:38   ` Jonathan Luntz
2003-03-31 19:17     ` Eli Zaretskii

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200304021414.h32EEY6Y025552@rum.cs.yale.edu \
    --to=monnier+gnu/emacs@rum.cs.yale.edu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).