[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [bug-gawk] $0 reassignment corruption in 4.2

From: Arnold Robbins
Subject: Re: [bug-gawk] $0 reassignment corruption in 4.2
Date: Fri, 24 Nov 2017 11:19:52 +0200
User-agent: Heirloom mailx 12.5 6/20/10

Hi All.

> Arnold -- does this look right to you? I haven't chased down all the
> nuances of what this assign function is doing...
> Note: we may have a similar ordering problem at debug.c:1301.

This seems to have been taken care of by the earlier change.
I could not produce a problem here.  (It's a little weird running
the gawk debugger from inside gdb... :-)

I think we're good.

> And at interpret.h:373, I'm not sure how Op_field_spec_lhs really works
> and what's going on with the field_assign value...
> Still a mystery to me.

The way to understand when an opcode is used is to see in awkgram.y
where it's generated.  The Op_xxx_lhs opcodes are used in cases
where a field, variable, or array element need to be able to be
assigned to. It's used for getline and also sub/gsub.

I didn't try to test anything but from the code, I think we're OK.



reply via email to

[Prev in Thread] Current Thread [Next in Thread]