Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Michael Snyder" <msnyder@cygnus.com>
To: gdb-patches@sources.redhat.com
Subject: Re: [PATCH]: multi-arch fix for monitor.c
Date: Wed, 05 Sep 2001 00:16:00 -0000	[thread overview]
Message-ID: <8e9m1d$8d3$1@cronkite.cygnus.com> (raw)
In-Reply-To: <39077F1C.4D2E@cygnus.com>


Michael Snyder wrote in message <39077F1C.4D2E@cygnus.com>...
>Andrew Cagney wrote:
>>
>> Andrew Cagney wrote:
>> >
>> > Michael Snyder wrote:
>> > >
>> > > OK, try #2:
>> > >
>> > > 2000-04-26  Michael Snyder  <msnyder@seadog.cygnus.com>
>> > >
>> > >         * monitor.c (monitor_fetch_register): MAX_REGISTER_RAW_SIZE
>> > >         is not static in the MULTI_ARCH world, so don't use it in a
>> > >         static array declaration.
>> >
>> > I'm not so sure :-(  MAX_REGISTER_RAW_SIZE can change and hence the
>> > allocated size of zerobuf could need to change.
>> >
>> > What about chaning its only use to write_register (..., 0)?
>>
>> Sorry, ignore this suggestion.  write_register is for high-level
>> accesses to GDB.  As Frank suggested, it would be safer to just create
>> the buffer when it is needed.
>
>That's why I keep you guys around.  ;-)
>Here is the new patch.

And then I see that I failed to include it.  Ok, HERE is the new patch:

2000-04-26  Michael Snyder  <msnyder@seadog.cygnus.com>

        * monitor.c (monitor_fetch_register): MAX_REGISTER_RAW_SIZE
        is not static in the MULTI_ARCH world, so don't use it in a
        static array declaration.


Index: monitor.c
===================================================================
RCS file: /cvs/src/src/gdb/monitor.c,v
retrieving revision 1.4
diff -c -r1.4 monitor.c
*** monitor.c   2000/04/04 02:08:52     1.4
--- monitor.c   2000/04/27 15:22:37
***************
*** 1206,1215 ****
       int regno;
  {
    char *name;
!   static char zerobuf[MAX_REGISTER_RAW_SIZE] =
!   {0};
!   char regbuf[MAX_REGISTER_RAW_SIZE * 2 + 1];
    int i;

    name = current_monitor->regnames[regno];
    monitor_debug ("MON fetchreg %d '%s'\n", regno, name ? name : "(null
name)")
;
--- 1206,1218 ----
       int regno;
  {
    char *name;
!   char *zerobuf;
!   char *regbuf;
    int i;
+
+   regbuf  = alloca (MAX_REGISTER_RAW_SIZE * 2 + 1);
+   zerobuf = alloca (MAX_REGISTER_RAW_SIZE);
+   memset (zerobuf, 0, MAX_REGISTER_RAW_SIZE);

    name = current_monitor->regnames[regno];
    monitor_debug ("MON fetchreg %d '%s'\n", regno, name ? name : "(null
name)")
;




  parent reply	other threads:[~2001-09-05  0:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200004262144.OAA05362@seadog.cygnus.com>
     [not found] ` <3907743C.BDD@cygnus.com>
2001-09-05  0:14   ` Frank Ch. Eigler
     [not found]   ` <39077739.62400899@cygnus.com>
     [not found]     ` <39077B95.D8EA5F06@cygnus.com>
     [not found]       ` <39077F1C.4D2E@cygnus.com>
2001-09-05  0:16         ` Michael Snyder [this message]
2001-09-05  0:15           ` Michael Snyder

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='8e9m1d$8d3$1@cronkite.cygnus.com' \
    --to=msnyder@cygnus.com \
    --cc=gdb-patches@sources.redhat.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