Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Stephane Carrez <Stephane.Carrez@worldnet.fr>
To: Andrew Cagney <ac131313@cygnus.com>
Cc: gdb-patches@sourceware.cygnus.com
Subject: Re: [RFA]: Fix TUI to build and run
Date: Tue, 17 Apr 2001 13:14:00 -0000	[thread overview]
Message-ID: <3ADCA50E.316A9DC4@worldnet.fr> (raw)
In-Reply-To: <3ADC7305.F1CDA2A8@cygnus.com>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 2051 bytes --]

Hi!

Andrew Cagney a écrit :
> 
> I hope you realise this is a political and not a technical question.
> Anyway, ignoring the politics ... :-)
> 

Yes... I did this not just to fix the build.

I really would like to have a curses-based GDB.  In some situations, it
really helps to have source window update while you step.

I have other patches to:

 - Cleanup defs.h to include only tui.h (and avoid inclusion of curses.h
   which breaks monitor.c and some others)
 - Improvement to install a specific Keymap in readline
   ('n' -> next, 's' -> step, 'c' -> continue, and so on)
 - Remove the __STDC__ stuff.


> The code contains a number extern additions in C files vis:
> 
> > diff -u -p -r1.5 tui.c
> > --- tui.c       2000/12/15 01:01:51     1.5
> > +++ tui.c       2001/03/25 16:55:30
> ...
> > +extern Function *old_rl_getc_function;
> 
> Just keep in mind that MI/libgdb are ment to eventually replace all
> those TUIDO macros.

Hum... there are more work but this could be interesting...

> 
> Anyway, on to the politics, nuff sitting on the fence.  Could I suggest:
> 
>         o       taging the GDB sources
>                 before anything goes in
> 
>         o       checking out a separate
>                 tree and then merging
>                 / committing the changes
>                 incrementally.
> 
>                 For instance, the patch to zap
>                 the __STDC__ stuff could
>                 be separated out.
> 
> Beyond that, assume you've got a licence to kill.
> 
>         Andrew

Well, I'm a little bit stuck because I can't generate patches as fast as 
I modify this code.

	Stephane

-----------------------------------------------------------------------
         Home                               Office
E-mail: stcarrez@worldnet.fr               Stephane.Carrez@sun.com
WWW:    http://home.worldnet.fr/stcarrez   http://www.sun.com
Mail:   17, rue Foucher Lepelletier        6, avenue Gustave Eiffel
        92130 Issy Les Moulineaux          78182 Saint Quentin en Yvelines
        France


      reply	other threads:[~2001-04-17 13:14 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-03-25  8:59 Stephane Carrez
2001-04-17 10:38 ` Andrew Cagney
2001-04-17 13:14   ` Stephane Carrez [this message]

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=3ADCA50E.316A9DC4@worldnet.fr \
    --to=stephane.carrez@worldnet.fr \
    --cc=ac131313@cygnus.com \
    --cc=gdb-patches@sourceware.cygnus.com \
    /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