From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mimir.eigenstate.org ([206.124.132.107]) by ewsd; Thu Jul  9 14:39:27 EDT 2020
Received: from abbatoir.fios-router.home (pool-74-101-2-6.nycmny.fios.verizon.net [74.101.2.6])
	by mimir.eigenstate.org (OpenSMTPD) with ESMTPSA id ef4f4a1f (TLSv1.2:ECDHE-RSA-AES256-SHA:256:NO);
	Thu, 9 Jul 2020 11:39:20 -0700 (PDT)
Message-ID: <9886E456A839F5CDF03974A2426A0518@eigenstate.org>
To: tlaronde@polynum.com, ori@eigenstate.org
CC: 9front@9front.org
Subject: Re: [9front] putc/fputc incorrect return?
Date: Thu, 9 Jul 2020 11:39:19 -0700
From: ori@eigenstate.org
In-Reply-To: <20200709182924.GA465@polynum.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
List-ID: <9front.9front.org>
List-Help: <http://lists.9front.org>
X-Glyph: ➈
X-Bullshit: object-oriented distributed self-signing factory-aware browser-scale dependency framework 


>> If you can post the code somewhere, I can also take a look.
> 
> Thank you, but I will have to reduce it because with the pecularities of
> RISK (the compilation framework) and the pecularities of the TeX web-to-raw-C
> translation process, you will waste a significant amount of time just to get
> your way around before succeeding to tackle the problem.
> 
> BTW, I tried to truss (with the acid program) the binary, but it gives
> absolutely no clue. I hit the problem with classic printf bisection on
> the resulting C files.
> 
> I will return back to it this week-end and will post an update (whether
> the hit on the core or some simplified code exhibiting the problem) at
> the begining of next week.
> 
> Best,

Sounds good, thanks for taking the time.