Mail Archives: djgpp-workers/1999/03/25/07:34:30
On 24 Mar 99, at 20:35, Eli Zaretskii wrote:
> From: Robert Hoehne <robert DOT hoehne AT gmx DOT net>
>
> This is (at least for me) a well know bug. It manifests itself, if you look
> in the corresponding sources for fsdb, edebug or gdb, where v2loadimage()
> is called, since there the commandline is passed as an array, where the
> [0]th character holds the length of the commandline which can represent
> of course only up to 255 characters. This can be solved using the !proxy
> methode, but I (and probably also others) hadn't the time and motivation
> to do the job [...]
>
> Note that the (not-so-easy) solution to this problem already exists--in
> go32-v2.c, it was done for v2.01. At the time I did that, I didn't
> realize that the same problem exists in the debugger support, so the
> solution is external to v2loadimage. But it should be a trivial
> matter to copy it to v2loadimage and have it work for the debuggers as
> well. Any volunteers?
I don't think it's trivial as v2loadimage() gets length of command line as
first byte of it and unless we are going to change this (and all places where
v2loadimage() is called) only way is to do it in places where v2loadimage is used.
>
> (If you want to know why this is a non-trivial problem, look at the
> comments inside go32-v2.c.)
>
Andris
- Raw text -