Mail Archives: djgpp/1994/05/04/10:18:23
> How does the !proxy method of passing command lines from stub.exe
> to go32.exe work? Does it just pass a pointer to go32 that
> points back into stub.exe's address space where the info is located? If
If the command line looks like this:
!proxy <argc> <argvseg> <argvofs> <stubinfoseg> <stubinfoofs>
Then go32 will load that info instead of trying to pass along the
command line. When libc calls system, it may generate a command line
like that with the data in the transfer buffer, so swapping would
toast it. That's why stub uses spawn instead of exec to call go32.
> so, then this could be a source of problems: Shell Room would
> swap that info out (well.. actually... go32.exe would over write
> it when it's loaded... but same net effect).
Yup.
> I suppose this would also affect my suggestion of using one of
> the swaplib functions used in the dos-only port of gnu make a few
> years back.
Yup.
- Raw text -