No registered users in community xowiki
in last 10 minutes
in last 10 minutes
Re: [Xotcl] xotcl crash
From: Stefan Sobernig <stefan.sobernig_at_wu.ac.at>
Date: Sat, 25 Jul 2009 15:16:08 +0200
> Message: 1
> Date: Fri, 24 Jul 2009 10:21:04 +0200
> From: Gustaf Neumann <neumann_at_wu.ac.at>
> Subject: Re: [Xotcl] xotcl crash
> To: Tibichte <zak_at_isa-software.com>
> Cc: xotcl_at_alice.wu-wien.ac.at
> Message-ID: <4A696EF0.7010906_at_wu.ac.at>
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>
> > 2- This forwarding method causes xotcl to crash:
> >
> > obj forward f2 list {%_at_end 13} %self %1
> >
> > ? { obj f2 1 2 3 }
>
> There is a bug in the current xotcl versions when both
> %_at_end and %1 is used, which will be fixed in the next release.
> The %1 means that the first argument from the provided
> argument list (here "1") will be placed at the given
> position. The argument is consumed and the remaining
> arguments (here "2" and "3") are appended to the arguments
> from the forward definition. S
The fact that %1 consumes = mutates the caller arg list and the %_at_POS
substitution operates on the mutated state of the resulting (=final)
list (kind of) made me think. And ... I guess I found the culprit of
this crashy interaction (see the patch attached):
once %1 consumes the first element of the caller arg list, the
currently arg handling mechanism for forwards counts %1 as an extra
arg in the overall arg list erroneously. however, it is rather a
placeholder for an already counted arg (=the first in the caller arg
list). This +1 overestimation in the internal assembly of the final
arg list led to a memory access violation for the %_at_POS substitution
under end offsets (end, end-1, end-2; in the Tcl sense of the word)
because end offsets require a correct total args count internally
(which used to report +1).
as for the patch: it is a minor and fairly non-invasive change. all
regression tests pass, i added some extra cases to test for the %1 +
%_at_POS-under-end-offsets interaction. the patch can be applied to the
a xotcl-1.6.3 source snapshot.
cheers
//stefan
Date: Sat, 25 Jul 2009 15:16:08 +0200
> Message: 1
> Date: Fri, 24 Jul 2009 10:21:04 +0200
> From: Gustaf Neumann <neumann_at_wu.ac.at>
> Subject: Re: [Xotcl] xotcl crash
> To: Tibichte <zak_at_isa-software.com>
> Cc: xotcl_at_alice.wu-wien.ac.at
> Message-ID: <4A696EF0.7010906_at_wu.ac.at>
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>
> > 2- This forwarding method causes xotcl to crash:
> >
> > obj forward f2 list {%_at_end 13} %self %1
> >
> > ? { obj f2 1 2 3 }
>
> There is a bug in the current xotcl versions when both
> %_at_end and %1 is used, which will be fixed in the next release.
> The %1 means that the first argument from the provided
> argument list (here "1") will be placed at the given
> position. The argument is consumed and the remaining
> arguments (here "2" and "3") are appended to the arguments
> from the forward definition. S
The fact that %1 consumes = mutates the caller arg list and the %_at_POS
substitution operates on the mutated state of the resulting (=final)
list (kind of) made me think. And ... I guess I found the culprit of
this crashy interaction (see the patch attached):
once %1 consumes the first element of the caller arg list, the
currently arg handling mechanism for forwards counts %1 as an extra
arg in the overall arg list erroneously. however, it is rather a
placeholder for an already counted arg (=the first in the caller arg
list). This +1 overestimation in the internal assembly of the final
arg list led to a memory access violation for the %_at_POS substitution
under end offsets (end, end-1, end-2; in the Tcl sense of the word)
because end offsets require a correct total args count internally
(which used to report +1).
as for the patch: it is a minor and fairly non-invasive change. all
regression tests pass, i added some extra cases to test for the %1 +
%_at_POS-under-end-offsets interaction. the patch can be applied to the
a xotcl-1.6.3 source snapshot.
cheers
//stefan