Memory access violation during code generation in WLBnodeOrIntGetNameOrval
|
|
Bugzilla Link |
483 |
Created on |
Apr 20, 2009 15:00 |
Resolution |
FIXED |
Resolved on |
Nov 20, 2009 01:27 |
Version |
1.00beta |
OS |
All |
Architecture |
PC |
Attachments |
aes.sac, valgrindop
|
Extended Description
sac2c: 16036 (the bug has at least existed throughout April)
Running sac2c -v2 aes.sac on the attachment causes a memory access violation on Linux and MacOS and a compiler crash. The -v argument must be 2 or greater. This happens in code generation. Note that if the comment labelled "comment" in the sac file is removed the problem goes away so maybe the problem starts in the scanner/parser?§
The sac code is not a stripped down version but even things like changing comments and removing unused functions fixes the crash.
Valgrind shows COMPwlsegx called during a code generation traverse so maybe somebody familiar with that area should take a look?