Unexpected use of &= causes error or crashes server

Description

We had a typo in some old code to concatenate a couple things that basically looked like this:

The mistake here is the second &= that should just be a &.

Under ACF 10, this works.

Under Lucee 5 running on Tomcat 8.5.3 on Windows, it crashes the whole server with a core dump that begins:

Under Linux, Tomcat is fine and Lucee reports a java.lang.verifyError error:

http://i.imgur.com/SsjncPc.png

Arguably, nobody has any business doing a &= b &= c to begin with, so this certainly isn't a priority, but given that it brought down Tomcat on our Windows box I figured I'd report my embarrassing typo that ACF let me get away with for so long.

Environment

Win 10 x64 / JRE 1.8.0 u91 & u92 (tomcat crashes, core dump)
Ubuntu Linux 16.x / JRE 1.8.0 u91 & u92 (lucee errors out with verifyLang Java error)

Activity

Zac Spitzer 
23 September 2017 at 04:13

seems ok on windows with 5.2.3.35 / Apache Tomcat/8.5.11

it's throwing java.lang.VerifyError

Details

Assignee

Reporter

Priority

New Issue warning screen

Before you create a new Issue, please post to the mailing list first https://dev.lucee.org

Once the issue has been verified, one of the Lucee team will ask you to file an issue

Affects versions

Created 30 June 2016 at 19:54
Updated 23 September 2017 at 04:13