From: Fernando Nasser <fnasser@cygnus.com>
To: Momchil Velikov <velco@fadata.bg>
Cc: GDB Patch List <gdb-patches@sourceware.cygnus.com>
Subject: Re: [Fwd: [patch] UDP transport support]
Date: Sat, 01 Apr 2000 00:00:00 -0000 [thread overview]
Message-ID: <38E4F1CD.9265272D@cygnus.com> (raw)
Message-ID: <20000401000000.D2mKW0fQjzUrji97Jan6EVNOmMqq92RC2ZvUsmsHtMc@z> (raw)
In-Reply-To: <38E39B66.3857BDFD@fadata.bg>
> Do you mind changing the syntax the parameter NAME to
> serial.c:serial_open () to
> tcp:<host>:<port>, and
> udp:<host>:<port>
> for TCP and UDP connections, respectively ?
Hi,
Please make sure tcp is assumed by default so the current behavior is not changed.
--
Fernando Nasser
Red Hat - Toronto E-Mail: fnasser@cygnus.com
2323 Yonge Street, Suite #300 Tel: 416-482-2661 ext. 311
Toronto, Ontario M4P 2C9 Fax: 416-482-6299
From kingdon@redhat.com Sat Apr 01 00:00:00 2000
From: Jim Kingdon <kingdon@redhat.com>
To: gdb-patches@sourceware.cygnus.com
Subject: Re: Patches to add i387 support to Solaris x86 platforms
Date: Sat, 01 Apr 2000 00:00:00 -0000
Message-id: <bu2iuisqt.fsf@rtl.cygnus.com>
References: <200002240845.JAA27280@reisser.regent.e-technik.tu-muenchen.de>
X-SW-Source: 2000-q1/msg00379.html
Content-length: 309
Hello again Peter! Funny that we've both ended up back on the GDB
beat after all these years.
> The following patches add i387 support for Solaris x86 platforms
I didn't see any problems with those patches.
I don't see a maintainer listed for Solaris x86, so I guess this falls
to Andrew or Stan.
From rearnsha@arm.com Sat Apr 01 00:00:00 2000
From: Richard Earnshaw <rearnsha@arm.com>
To: Scott Bambrough <scottb@netwinder.org>
Cc: rearnsha@arm.com
Subject: Re: RFC: Patch to arm-tdep.c -- Register flavors
Date: Sat, 01 Apr 2000 00:00:00 -0000
Message-id: <200002161539.PAA12704@cam-mail2.cambridge.arm.com>
References: <38AAC291.38C9F512@netwinder.org>
X-SW-Source: 2000-q1/msg00182.html
Content-length: 1027
> > And finally, the ps register name is wrong, especially in the A{T}PCS area
> > but also more generally; the name is "cpsr" in all ARM documentation (the
> > "ps" name comes from when the processor flags weren't really a separate
> > register -- they were in the unused parts of r15 -- so there was no name).
>
> Richard is correct here, in arm-linux-nat.c, I initialize the PS register with
> the contents of CPSR if arm_apcs_32 is set, or with the contents of the PC if
> not. Perhaps we should set the register name based on this information as well.
This is one of the few cases where I would just delete the old name. Old
processors never had a specific flags register, so the 'ps' name was
'invented' by the original porter of gdb. Since then the cpsr name has
come into use and I doubt that even users debugging in 26-bit mode would
object violently to this name changing (maybe we can support "ps" as an
alias when parsing user input, but I see no point in ever printing
anything other than "cpsr".
R.
next parent reply other threads:[~2000-04-01 0:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <38E39B66.3857BDFD@fadata.bg>
2000-03-31 10:43 ` Fernando Nasser [this message]
2000-04-01 0:00 ` Fernando Nasser
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=38E4F1CD.9265272D@cygnus.com \
--to=fnasser@cygnus.com \
--cc=gdb-patches@sourceware.cygnus.com \
--cc=velco@fadata.bg \
/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