From: "Steven Levine" <ecs-isp@2rosenthals.com>
Message-ID: <677b97e2.4.mr2ice.fgrirsq@earthlink.net>
Date: Mon, 06 Jan 2025 00:44:18 -0800
To: "eCS ISP Mailing List" <ecs-isp@2rosenthals.com>
In-Reply-To: <list-11710902@2rosenthals.com>
Subject: Re: [eCS-ISP] Getting started with Let's Encrypt

In <list-11710902@2rosenthals.com>, on 01/05/25
   at 09:11 PM, "Peter Moylan" <ecs-isp@2rosenthals.com> said:

Hi Peter,

>That brings up an interesting point. The linker map shows code addresses,
>but I've never given much thought to where the data and stack segments
>go. I'll have to take a look with the debugger.

They are all in lower memory (i.e. in the first 512MB of address space).
As you know, it's possible to put code and data in upper memory, but none
of your code that I have seen does this.

>But only in this one special case. The procedure in question is what I
>use when logging to the screen, and many other log lines go through
>without a problem. It's just the one rare case where there's a failure.

I'm familiar with the code you refer to, which I why I suggested you
modify your problematic code to work the same way.

>Next, I implemented your suggestion of making WriteString call
>WriteStringAt. This worked. Thank you. I don't know why it worked,

I still suspect the modula is not thunking the pointer correctly.  I'd
need to see a testcase of your failing code to say more.

>Maybe later. For now, thanks to your suggestion, I have a useful debugger
>again, so I can proceed to the bug that I was originally trying to track.

:-)


Steven

-- 
----------------------------------------------------------------------
"Steven Levine" <steve53@earthlink.net>  Warp/DIY/BlueLion etc.
www.scoug.com www.arcanoae.com www.warpcave.com
----------------------------------------------------------------------