Date:	Mon, 2 Jul 2001 08:56:37 +0300 (IDT)
From:	Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender:	eliz AT is
To:	"Mark E." <snowball3 AT bigfoot DOT com>
cc:	djgpp-workers AT delorie DOT com
Subject:	Re: v2loadimage proxy rev 3
In-Reply-To:	<3B3F5BE9.21153.2517F9@localhost>
Message-ID:	<Pine.SUN.3.91.1010702085334.3012A@is>
MIME-Version:	1.0
Reply-To:	djgpp-workers AT delorie DOT com
Errors-To:	nobody AT delorie DOT com
X-Mailing-List:	djgpp-workers AT delorie DOT com
X-Unsubscribes-To:	listserv AT delorie DOT com

On Sun, 1 Jul 2001, Mark E. wrote:

> > I'm uneasy about this dummy command line: what if the debuggee somehow
> > disables the !proxy support in its startup code?
> 
> Didn't think of that. What about this?
> 
>   if (proxy_mode)
>   {
>     unsigned char cmd_len;
> 
>     /* Setup the transfer buffer with proxy arguments.  */
>     make_proxy_buffer(program, cmdline + 1, proxy_argc, __tb, __tb_size);
> 
>     /* Provide a fallback command line in case the debugee has disabled
>        the proxy method.  */
>     cmd_len = __strnlen(cmdline + 1, 126);
>     _farpokeb(my_ds, si.psp_selector + 128, cmd_len);
>     movedata(my_ds, (unsigned)(cmdline + 1), si.psp_selector, 128 + 1, cmd_len);
>     _farpokeb(my_ds, si.psp_selector + 128 + 1 + cmd_len, '\r');
>   }

This is fine, but where is __strnlen?  Is this some new function in
the current CVS?  I don't see it.

- Raw text -