From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <zsh-users-return-20788-mason-zsh=primenet.com.au@zsh.org>
Received: (qmail 20571 invoked by alias); 18 Oct 2015 11:30:16 -0000
Mailing-List: contact zsh-users-help@zsh.org; run by ezmlm
Precedence: bulk
X-No-Archive: yes
List-Id: Zsh Users List <zsh-users.zsh.org>
List-Post: <mailto:zsh-users@zsh.org>
List-Help: <mailto:zsh-users-help@zsh.org>
X-Seq: 20788
Received: (qmail 11114 invoked from network); 18 Oct 2015 11:30:15 -0000
X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on f.primenet.com.au
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,FREEMAIL_FROM,
	T_DKIM_INVALID autolearn=ham autolearn_force=no version=3.4.0
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.ru; s=mail;
	t=1445167152; bh=QTN9rojVmPsBuQb6xnf5uTNeMoQ0GJMF30TCZP6McVw=;
	h=From:To:In-Reply-To:References:Subject:Date;
	b=swBAamQSIa935M4mW+6/D/7K59V37dqYuMMxLiIspSHCzsAhXNWSrkNxLGSTRM1Va
	 zzc1E2IQK6BjiXFsKX8Jxjt0zljpg+fIAZwUKi4YE67m0SmNemj4EvfmIx4KW9Yp5T
	 6c02bjPrf81zA/NyCa1Tn3BLm4RtqAAmS2VFwW/g=
From: ZyX <kp-pav@yandex.ru>
To: Ray Andrews <rayandrews@eastlink.ca>,
	"zsh-users@zsh.org" <zsh-users@zsh.org>
In-Reply-To: <562320B7.6060200@eastlink.ca>
References: <5622DC5B.20103@eastlink.ca> <2507441445128151@web27o.yandex.ru> <562320B7.6060200@eastlink.ca>
Subject: Re: following a variable's value.
MIME-Version: 1.0
Message-Id: <877541445167151@web30o.yandex.ru>
X-Mailer: Yamail [ http://yandex.ru ] 5.0
Date: Sun, 18 Oct 2015 14:19:11 +0300
Content-Transfer-Encoding: 8bit
Content-Type: text/plain; charset=utf-8

18.10.2015, 07:33, "Ray Andrews" <rayandrews@eastlink.ca>:
> On 10/17/2015 05:29 PM, ZyX wrote:
>>  18.10.2015, 03:11, "Ray Andrews" <rayandrews@eastlink.ca>:
>>>  Gentlemen,
>>>
>>>  I discovered by accident the useful 'warncreateglobal' and it has me in
>>>  mind to ask if there's some way of tracing the value of variable. I
>>>  know about 'set -x' of course, but some way of following the fortunes of
>>>  a single variable would be very nice.
>
> ...
>>  If you write C module specifically for your needs you may overcome these limitations.
>
> Thanks ZyX, but that sounds way over my head. I've still never touched
> python. If no one else has any ideas then I'll keep doing it the hard
> way with inserted queries.

You can use some other languages which allow compiling *.so libraries and have a way to create compatible ABI: e.g. Rust. But in any case basic C knowledge is necessary.

What do you mean by “inserted queries”? Some kind of “debugging printf”?