Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

yy_bs_lineno and yy_bs_column not initialized in yy_scan_buffer #70

Open
SteveWaggoner opened this issue Apr 11, 2016 · 4 comments
Open

yy_bs_lineno and yy_bs_column not initialized in yy_scan_buffer #70

SteveWaggoner opened this issue Apr 11, 2016 · 4 comments
Labels
bug scanner
Milestone
2.7.0

Comments

@SteveWaggoner
Copy link

For sure, this bug is in flex-2.5.37 and in looking at the source for the latest it's still there.
https://sourceforge.net/p/flex/bugs/180/
@westes westes modified the milestone: 2.7.0 Jul 3, 2017
@jannick0
Copy link
Contributor

Would that issue disappear by replacing malloc by calloc, which by default zero-initializes? If implemented, then only non-zero member initializations would be needed.

@jannick0
Copy link
Contributor

jannick0 commented Dec 14, 2017 •
edited
Loading

This should be fixed by PR #295 where all internal flex structures are zero-initialized.

happyCoder92 added a commit to google/kafel that referenced this issue Sep 26, 2018
@happyCoder92
Add a workaround for flex locations bug
54382d2 
westes/flex#70
@graywolf
Copy link

graywolf commented Jun 8, 2019

Is there anything I can do to help getting this resolved? I just noticed this after some debugging so it would be nice to have this fixed.

sethterashima pushed a commit to sethterashima/kafel that referenced this issue Jul 17, 2019
@happyCoder92
Add a workaround for flex locations bug
b3c476d 
westes/flex#70
@smore-lore
Copy link

Also seeing this. For consistency, it seems that the workaround should initialize yy_bs_lineno to 1 and yy_bs_column to 0.

eric-s-raymond added a commit to eric-s-raymond/flex that referenced this issue Oct 7, 2020
@eric-s-raymond
Update the documentation on writing a back end,
8da857a 
It will doubtless need expansion and revision when we actually
write one.

No diffs in generated test code.

westes#70 and last in the retargeting patch series
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug scanner
Projects
None yet
Milestone
2.7.0
Development

No branches or pull requests
5 participants
@graywolf @westes @jannick0 @SteveWaggoner @smore-lore