From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <zsh-workers-return-33749-mason-zsh=primenet.com.au@zsh.org>
Received: (qmail 23178 invoked by alias); 22 Nov 2014 05:27:25 -0000
Mailing-List: contact zsh-workers-help@zsh.org; run by ezmlm
Precedence: bulk
X-No-Archive: yes
List-Id: Zsh Workers List <zsh-workers.zsh.org>
List-Post: <mailto:zsh-workers@zsh.org>
List-Help: <mailto:zsh-workers-help@zsh.org>
X-Seq: 33749
Received: (qmail 24139 invoked from network); 22 Nov 2014 05:27:23 -0000
X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on f.primenet.com.au
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_LOW
	autolearn=ham version=3.3.2
X-Authority-Analysis: v=2.1 cv=AduIQRnG c=1 sm=1 tr=0
 a=SBdK3agBVlyT/P6vVha89Q==:117 a=SBdK3agBVlyT/P6vVha89Q==:17 a=G8GL833Es-AA:10
 a=N659UExz7-8A:10 a=BOrEfmTbm0bCEhhyFkYA:9 a=pILNOxqGKmIA:10
Message-id: <54701EB8.4030500@eastlink.ca>
Date: Fri, 21 Nov 2014 21:27:20 -0800
From: Ray Andrews <rayandrews@eastlink.ca>
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:31.0) Gecko/20100101 Icedove/31.2.0
MIME-version: 1.0
To: zsh-workers@zsh.org
Subject: Re: trouble with debugging binary
References: <930.1416260160@thecus.kiddle.eu>
 <42F4E5F2-97E7-4803-87CB-B1C67CD943B2@kba.biglobe.ne.jp>
 <15511.1416528068@thecus.kiddle.eu> <546E9224.7090709@eastlink.ca>
 <CAHYJk3Tca_aAn5mjtGb24DDeor28Jk+M9aBYLQhC__Y5-BubUQ@mail.gmail.com>
 <546EA58F.7010101@eastlink.ca> <141120222353.ZM10495@torch.brasslantern.com>
 <546F7646.7080108@eastlink.ca> <141121204545.ZM11623@torch.brasslantern.com>
In-reply-to: <141121204545.ZM11623@torch.brasslantern.com>
Content-type: text/plain; charset=windows-1252; format=flowed
Content-transfer-encoding: 7bit

    Sadly, rebuilding without --enable-zsh-debug is sort of like
    removing the batteries from your smoke detector. There may still be
    a fire, but you just aren't hearing about it any more.


I just played with --enable-zsh-debug a bit more, and funny thing is 
that the errors
sorta just go away after a while, if you give it time.  By the third 
attempt at a
completion, everything is just fine. God knows.

    pts/5 HP-y5--5-Debian1 root /aMisc/Ray1/Src $ ./zsh,1,debugging
    zsh-5.0.7-86-ga3cc409
    6: text.c:865: unknown word code in gettext2()
    1: text.c:865: unknown word code in gettext2()
    7: text.c:865: unknown word code in gettext2()
    8: text.c:865: unknown word code in gettext2()

... but it always does that on starting that binary.

Fiddling with it:

    typeset -g TLC
    TRAPDEBUG()
    {
    }

... even when the function is empty, the error is still there.