From: Fernando Nasser <fnasser@cygnus.com>
To: David Taylor <taylor@cygnus.com>
Cc: gdb-patches@sourceware.cygnus.com
Subject: Re: RFA: Small fix to valops.c (value_assign)
Date: Mon, 12 Jun 2000 07:33:00 -0000 [thread overview]
Message-ID: <3944F45F.D58F41@cygnus.com> (raw)
In-Reply-To: <200006121414.KAA01113@texas.cygnus.com>
David Taylor wrote:
>
> Date: Fri, 09 Jun 2000 00:57:07 +0000
> From: Fernando Nasser <fnasser@cygnus.com>
>
> This causes some spurious register reads (sometimes to a invalid
> register number) on some targets when reading fields of typed registers
> that are not on the first byte of the register.
>
> I assume that you mean that it *PREVENTS* some spurious register reads...
I meant "caused"... but you are right, "prevents" makes it clearer.
At least I was more fortunate with the ChangeLog entry wording...
--
Fernando Nasser
Red Hat Canada Ltd. 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 spolk@redhat.com Mon Jun 12 10:34:00 2000
From: Syd Polk <spolk@redhat.com>
To: Chris Faylor <cgf@cygnus.com>, gdb-patches@sourceware.cygnus.com
Cc: spolk@cygnus.com, fnasser@cygnus.com
Subject: Re: [RFA] Missed one place to search for /usr/share in gdbtk
Date: Mon, 12 Jun 2000 10:34:00 -0000
Message-id: <4.2.0.58.20000612103509.00a299d0@pop.cygnus.com>
References: <20000609204522.A31630@cygnus.com>
X-SW-Source: 2000-06/msg00139.html
Content-length: 1107
This looks good.
At 08:45 PM 6/9/00 -0400, Chris Faylor wrote:
>I don't know how I missed this one but *today* I need an additional patch
>to get gdbtk working.
>
>Ok to check in?
>
>cgf
>
>Fri Jun 9 20:43:40 2000 Christopher Faylor <cgf@cygnus.com>
>
> * src/paths.c (initialize_paths): Look in /usr/share for stuff.
>
>
>Index: src/paths.c
>===================================================================
>RCS file: /cvs/src/src/libgui/src/paths.c,v
>retrieving revision 1.2
>diff -u -p -r1.2 paths.c
>--- paths.c 2000/04/03 19:34:38 1.2
>+++ paths.c 2000/06/10 00:43:30
>@@ -68,6 +68,9 @@ proc initialize_paths {} {\n\
> }\n\
> cd [file dirname $exec_name]\n\
> # Handle build with --exec-prefix and build without.\n\
>+ set d [file join [file dirname [pwd]] usr share]\n\
>+ lappend prefdirs $d\n\
>+ lappend guidirs [file join $d cygnus gui]\n\
> set d [file join [file dirname [pwd]] share]\n\
> lappend prefdirs $d\n\
> lappend guidirs [file join $d cygnus gui]\n\
Syd Polk spolk@redhat.com
Engineering Manager +1 415 777 9810 x 241
Red Hat, Inc.
prev parent reply other threads:[~2000-06-12 7:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-06-12 7:15 David Taylor
2000-06-12 7:33 ` Fernando Nasser [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=3944F45F.D58F41@cygnus.com \
--to=fnasser@cygnus.com \
--cc=gdb-patches@sourceware.cygnus.com \
--cc=taylor@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