Re: Pascal language support patch preparation

[Eli Zaretskii <eliz@delorie.com>]

>  the diffs are mainly due to the reformating thus it is very difficult to
>  find out where the code really did change!!

Use "diff -cbBw", and you will see mostly real code changes.

But do NOT send diffs generated by "diff -cbBw", as they will most
probably fail to apply.  Instead, after you have seen what/where are
the real code changes, and copied them to the p-*.* files, make the
diffs with the normal "diff -c" command.
From kettenis@wins.uva.nl Sat Apr 01 00:00:00 2000
From: Mark Kettenis <kettenis@wins.uva.nl>
To: muller@cerbere.u-strasbg.fr
Cc: gdb@sourceware.cygnus.com
Subject: Re: Indent -gnu ?
Date: Sat, 01 Apr 2000 00:00:00 -0000
Message-id: <200003021321.e22DLrF00601@delius.kettenis.local>
References: <200003021257.NAA00259@cerbere.u-strasbg.fr>
X-SW-Source: 2000-q1/msg00498.html
Content-length: 1236

   Date: Thu, 02 Mar 2000 13:41:58 +0100
   From: Pierre Muller <muller@cerbere.u-strasbg.fr>

      I want to format my PATCH for pascal extension before submitting it 
   so I read that I should use GNU indent with -gnu option !

Hi Pierre, I do hope that you'll break your patch up in some smaller
chunks.  IMHO the fact that you sent it as a large chunk, was one of
the main reasons why it was ignored last fall.  

     But I tried this on c-lang.h just to see
   and the result is that the current header file does not conform to 
   indent output !

Looks like you're using a different `indent' than was used on the GDB
sources.  I think, this shows that defining the GDB coding standards
in terms of the output of `indent' is not really workable.  I've also
noticed that `indent' sometime really messes up the output, because it
gets confused by certain constructs.

     So my question is simply should I run indent on my files
   or should I send them without !

I'd say that avoiding gratuitous reformatting is more important than
running your changes through `indent'.  Thus, make sure that your
patches only contains changes for code you really changed, and that
these changes correspond to the GNU coding standards.

Mark
From ac131313@cygnus.com Sat Apr 01 00:00:00 2000
From: Andrew Cagney <ac131313@cygnus.com>
To: rganesan@myrealbox.com
Cc: "Insight (GDB GUI)" <insight@sourceware.cygnus.com>, GDB Discussion <gdb@sourceware.cygnus.com>
Subject: Re: GDB snapshot changes
Date: Sat, 01 Apr 2000 00:00:00 -0000
Message-id: <38E1A781.DE684A21@cygnus.com>
References: <38D72679.BAD97DCD@cygnus.com> <14551.20952.137585.56767@anamika>
X-SW-Source: 2000-q1/msg00833.html
Content-length: 1029

Ganesan R wrote:
> 
> >>>>> "Andrew" == Andrew Cagney <ac131313@cygnus.com> writes:
> 
> > [Sorry for the cross post.  Please set followups to
> > gdb@sourceware.cygnus.com]
> 
> > Hello,
> 
> > Firstly, I'm pleased to report that nightly snapshots appear to be
> > working reliably.  See the directory:
> >       ftp://sourceware.cygnus.com/pub/gdb/snapshots/
> > For those that are curious, ``-D'' is used so that while each snapshot
> > is created during the afternoon, it contains the sources from exactly
> > ``00:00 GMT'' each morning.
> 
> Hi,
> 
> I am missing the CVS "ready" snapshots, I mean the snapshots which I can
> unpack and then do a cvs update on them to keep in sync. Any plans to
> put them back?

I've changed things so that there are be weekly CVS snapshots (more
frequent is of marginal benefit as the first thing you do is cvs update
anyway :-).

In addition, starting tomorrow the nightly snapshots will include md5
sums.

If, after a week, none of this appears to be true, please let me know.

	Andrew
From nikulin@actsw.amat.com Sat Apr 01 00:00:00 2000
From: "Serge Nikulin" <nikulin@actsw.amat.com>
To: <gdb@sourceware.cygnus.com>
Subject: How to set RS232 speed in gdb in WinNT?
Date: Sat, 01 Apr 2000 00:00:00 -0000
Message-id: <003e01bf9b69$afc0c220$35758798@mis.amat.com>
X-SW-Source: 2000-q1/msg00852.html
Content-length: 877

Hi,

I use gdb for remote debugging of m68k target, compiled with MRI
<--host=i686-pc-cygwin32 --target=m68k-motorola-ieee>
Native MRI' X-Ray debugger does not support our home-made RTOS.
GDB works but I have few questions.

1) Currently ieee-695 bfd section is not connected to gdb, so I work without
src.
    I've checked examples of coff and aout conections and it does not look
as a 1-day job for me
    (including the fact that ieee-695 support in bfd is incomplete).
    Does anyone have ieee + gdb experience?

2) In my gdb session under WinNT I use command "target remote com1"
In this case gdb connects to COM1 at 9600 baud. I'd like to change this
speed (say, to 38400) but I can't. I've changed default speed for COM1 in
WinNT's control panel but it did not help. It looks like I have to pass that
speed to cygwin.dll somehow. How can I do that?

Thanks!

Serge.