Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Josef Ezra" <jezra@emc.com>
To: <gdb-patches@sources.redhat.com>
Subject: Re: bug in tracepoint protocol implementation
Date: Tue, 03 Oct 2000 10:29:00 -0000	[thread overview]
Message-ID: <00e601c02d5f$37d45820$6c219fa8@lss.emc.com> (raw)
In-Reply-To: <39D8D1CE.3059@redhat.com>

[-- Attachment #1: Type: text/plain, Size: 1708 bytes --]

(Thanks  Michael, I'll try to hit standards this time)

The attached fixes an unpleasant bug in trace mechanism. Creating a
tracepoint declaration string for remote host, and when more then one
memrange item was declared in a tracepoint, the debugger would have leave
gaps in the string's buffer, causing unexpected results.

Josef Ezra

----- Original Message -----
From: "Michael Snyder" <msnyder@redhat.com>
To: "Josef Ezra" <jezra@emc.com>
Cc: <gdb-patches@sources.redhat.com>; <shagam@emc.com>; <sgordon@emc.com>
Sent: Monday, October 02, 2000 2:19 PM
Subject: Re: bug in tracepoint protocol implementation


> Josef Ezra wrote:
> >
> > hi
> >
> > file: tracepoint.c
> > function: stringify_collection_list
> >
> > old:
> >    count += strlen (end);
> >    end += count ;
> >
> > new:
> >     count += strlen (end);
> >     end = temp_buf + count ;
> >
> > reasoning:
> > When saving more then one memrange parameter, the old code
> > leaves 'gaps' in the temp_buf string.
>
> Josef,
>
> Your change is correct (thank you).  However, would you
> please re-submit it after consulting the file "CONTRIBUTING"
> in your gdb source directory?  Or see:
> http://sources.redhat.com/gdb/#contribute
>
> Briefly, to streamline the process of accepting GDB
> contributions, we request the following format:
>
>   * brief description of the problem being addressed
>   * ChangeLog entry
>   * Diff of the changes, such as will be acceptable
>     as input to "patch" (eg. "cvs diff -c3p tracepoint.c")
>
> Hate to put you thru the exercise of resubmitting such a
> simple patch, but it will be good experience if you intend
> to make further GDB contributions (as I hope you will).
>
> Thanks,
> Michael Snyder
>

[-- Attachment #2: tracepoint.c.diff --]
[-- Type: text/plain, Size: 655 bytes --]



    *tracepoint.c : bug fixed: string was created in bogus
                              offsets.



*** tracepoint.c.~1.1~	Tue Oct  3 12:55:06 2000
--- tracepoint.c.~1.1~~	Tue Oct  3 12:56:34 2000
*************** stringify_collection_list (list, string)
*** 1448,1454 ****
  	       (long) (list->list[i].end - list->list[i].start));
  
        count += strlen (end);
!       end += count;
      }
  
    for (i = 0; i < list->next_aexpr_elt; i++)
--- 1448,1454 ----
  	       (long) (list->list[i].end - list->list[i].start));
  
        count += strlen (end);
!       end = temp_buf + count;
      }
  
    for (i = 0; i < list->next_aexpr_elt; i++)

  reply	other threads:[~2000-10-03 10:29 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-10-02 11:04 Josef Ezra
2000-10-02 11:20 ` Michael Snyder
2000-10-03 10:29   ` Josef Ezra [this message]
     [not found]   ` <004e01c039d8$774c1d50$6c219fa8@lss.emc.com>
2000-10-19 10:32     ` tracepoints implementation: bug in byte code generating Michael Snyder
     [not found]       ` <005b01c039f6$f46b1390$6c219fa8@lss.emc.com>
2000-10-19 11:06         ` Michael Snyder
     [not found]           ` <006101c039f9$df09df60$6c219fa8@lss.emc.com>
     [not found]             ` <5mvguo5spm.fsf@jtc.redback.com>
     [not found]               ` <008501c03aad$46c9d700$6c219fa8@lss.emc.com>
     [not found]                 ` <39F090F3.2DDC@redhat.com>
     [not found]                   ` <009001c03adb$b46a7b60$6c219fa8@lss.emc.com>
2000-10-20 14:54                     ` Michael Snyder
     [not found]                       ` <003d01c03b0e$42568040$961919ac@lss.emc.com>
     [not found]                         ` <39F47D62.2B5B@redhat.com>
     [not found]                           ` <004001c03d2c$14209970$6c219fa8@lss.emc.com>
2000-10-23 13:18                             ` 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='00e601c02d5f$37d45820$6c219fa8@lss.emc.com' \
    --to=jezra@emc.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