public inbox for insight@sourceware.org
 help / color / mirror / Atom feed
From: Keith Seitz <keiths@redhat.com>
To: Roland Schwingel <roland@onevision.com>
Cc: insight@sourceware.org
Subject: Re: [PATCH] Remove deprecated access to tcl internal variables
Date: Fri, 23 Mar 2012 22:25:00 -0000	[thread overview]
Message-ID: <4F6CF842.7030400@redhat.com> (raw)
In-Reply-To: <4F671C73.2020308@onevision.com>

I noticed this a while back, too.. Some small nits.

In the future, could you please
add "-p" option to diff? I have "diff -upN" set in my .cvsrc. It gives 
me a little more context when reading the patch.

On 03/19/2012 04:45 AM, Roland Schwingel wrote:
> --- gdbtk_orig/generic/gdbtk.c	2012-03-19 11:21:15.542232400 +0100
> +++ gdbtk/generic/gdbtk.c	2012-03-19 11:23:12.099170600 +0100
> @@ -494,17 +494,17 @@
>     make_final_cleanup (gdbtk_cleanup, NULL);
>
>     if (Tcl_Init (gdbtk_interp) != TCL_OK)
> -    error ("Tcl_Init failed: %s", gdbtk_interp->result);
> +    error ("Tcl_Init failed: %s", Tcl_GetStringResult(gdbtk_interp));

Watch the spaces in between function names and open parenthesis. This is 
a GNU convention (which we follow). That should be "Tcl_GetStringResult 
(gdbtk_interp)".

There are several places where this occurs throughout the patches (and 
subsequent ones).

> tcl_compat_gdbtk-hooks.c.patch
>
>
> --- gdbtk_orig/generic/gdbtk-hooks.c	2012-01-03 13:26:56.000000000 +0100
> +++ gdbtk/generic/gdbtk-hooks.c	2012-03-05 11:47:03.340565000 +0100
> @@ -254,17 +254,22 @@
>   	{
>   	  report_error ();
>   	  actual_len = 0;
> +	  buf[0] = '\0';
> +	  return 0;

This hunk is not mentioned in the ChangeLog.

I don't understand this. If we return 0 here, that means that no bytes 
in the buffer were filled-in, yet we are actually filling in one byte 
anyway. Is there a problem this was designed to solve? Is the return 
value not being checked somewhere or buf assumed to have at least the 
string terminal in it?

>   	}
>         else
> -        actual_len = strlen (gdbtk_interp->result);
> +      {
> +      	const char *tclResult = Tcl_GetStringResult(gdbtk_interp);
> +        actual_len = strlen (tclResult);
>
>         /* Truncate the string if it is too big for the caller's buffer.  */
>         if (actual_len>= sizeof_buf)
>   	actual_len = sizeof_buf - 1;
>
> -      memcpy (buf, gdbtk_interp->result, actual_len);
> +      memcpy (buf,tclResult, actual_len);
>         buf[actual_len] = '\0';
>         return actual_len;
> +     }
>       }
>     else
>       {

Keith

  reply	other threads:[~2012-03-23 22:25 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-19 11:46 Roland Schwingel
2012-03-23 22:25 ` Keith Seitz [this message]
2012-03-27  7:13 Roland Schwingel
2012-03-27 15:18 ` Keith Seitz
2012-03-28 14:53 Roland Schwingel

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=4F6CF842.7030400@redhat.com \
    --to=keiths@redhat.com \
    --cc=insight@sourceware.org \
    --cc=roland@onevision.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).