Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Frederic RISS <frederic.riss@st.com>, gdb-patches@sourceware.org
Subject: Re: [RFC] Don't lose compilation directory in Dwarf2 line-tables
Date: Fri, 14 Apr 2006 14:58:00 -0000	[thread overview]
Message-ID: <20060414145802.GA15732@nevyn.them.org> (raw)
In-Reply-To: <ur7401bm2.fsf@gnu.org>

On Fri, Apr 14, 2006 at 05:21:41PM +0300, Eli Zaretskii wrote:
> > Really? my checkout from yersterday still asks me :
> > (gdb) dir
> > Reinitialize source path to empty? (y or n) y
> > 
> > Source directories searched: $cdir:$cwd
> 
> Right you are, but this raises an issue with the Windows port (where I
> originally checked this): it does NOT ask for permission.
> 
> [Time passes...]  Ah, I see, it's probably because
> input_from_terminal_p returns zero on Windows.  Is this fixable?

How current is your binary, and what are you running it in?  And what's
the host platform configured as?

If it's a MinGW32-hosted GDB, and you're running it in a DOS console,
and the binary is more than a few months old, than this is an expected
and fixed bug; try a current CVS.  If this is a DJGPP binary running
in a Windows console, then I'm not really sure what to do.  I haven't
tried that.  You'd have to do something similar to what I did for
mingw32.

The problem came in gdb_has_a_terminal.  You have to have serial_fdopen
work on the console, and you have to be able to get the terminal state
from the result.

> Anyway, I think we should modify the prompt to say this:
> 
>   Reinitialize source path to default? (y or n)
> 
> Does anyone disagree?

This sounds good to me.

-- 
Daniel Jacobowitz
CodeSourcery


  reply	other threads:[~2006-04-14 14:58 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-13 11:25 [RFC] Don't loose " Frederic RISS
2006-04-13 17:49 ` Jim Blandy
2006-04-14  7:32   ` [RFC] Don't lose " Frederic RISS
2006-04-14  7:41     ` Jim Blandy
2006-04-14  8:23       ` Frederic RISS
2006-04-14 14:04         ` Daniel Jacobowitz
2006-04-14 14:51           ` Frederic RISS
2006-04-18 12:32             ` Frederic RISS
2006-04-18 13:04               ` Daniel Jacobowitz
2006-04-18 14:00                 ` Frederic RISS
2006-04-20 16:27                   ` Daniel Jacobowitz
2006-04-21  7:14                     ` Frederic RISS
2006-04-21  1:10                   ` Jim Blandy
2006-04-21  8:35                     ` Frederic RISS
2006-04-21 16:46                       ` Jim Blandy
2006-04-21 17:00                         ` Frederic RISS
2006-04-24 12:49                         ` Andrew STUBBS
2006-04-14  8:44     ` Eli Zaretskii
2006-04-14 11:44       ` Frederic RISS
2006-04-14 13:08         ` Eli Zaretskii
2006-04-14 13:42           ` Frederic RISS
2006-04-14 14:21             ` Eli Zaretskii
2006-04-14 14:58               ` Daniel Jacobowitz [this message]
2006-04-14 15:03                 ` Eli Zaretskii
2006-04-14 18:39               ` Frédéric Riss
2006-04-13 19:58 ` [RFC] Don't loose " Jason Molenda

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

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

  git send-email \
    --in-reply-to=20060414145802.GA15732@nevyn.them.org \
    --to=drow@false.org \
    --cc=eliz@gnu.org \
    --cc=frederic.riss@st.com \
    --cc=gdb-patches@sourceware.org \
    /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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox