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.

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

Segmentation fault on MultiFlex when processing a dictionary with duplicate semantic codes #1

Closed
martinec opened this Issue Apr 1, 2016 · 1 comment

Comments

Projects
None yet
2 participants
@martinec
Member

martinec commented Apr 1, 2016

MultiFlex crashes when processing a dictionary that has a duplicate semantic code:

What steps will reproduce the problem?

UnitexToolLogger MultiFlex Users/Lucie.Steible/Desktop/test.unitex.txt -oUsers/Lucie.Steible/Desktop/test.unitexflx.dic -aUsers/Lucie.Steible/Documents/Unitex-GramLab/Unitex/Alsatian/Alphabet.txt -dUsers/Lucie.Steible/Desktop/Seafile/RESTAURE/ressources/lexiques/DELA/test/Alsatian/Inflection -qutf8-no-bom

What is the expected output?

Done.

What do you see instead?

In graph V6 label format incorrect in :P3s (at position 0):  '<'  expected.
Segmentation fault

More info

@martinec martinec changed the title from Segmentation fault on MultiFlex when a dictionary has a duplicate semantic code to Segmentation fault on MultiFlex when processing a dictionary with duplicate semantic codes Apr 2, 2016

@martinec martinec added this to the 3.2-beta milestone Apr 2, 2016

@hghwng

This comment has been minimized.

Show comment
Hide comment
@hghwng

hghwng Apr 7, 2016

Contributor

Fixed in #5.

To have consistent behavior on duplicate semantic codes with DELAS parser, error messages are displayed by DELAC parser, instead of silently ignoring the duplicate code.

Contributor

hghwng commented Apr 7, 2016

Fixed in #5.

To have consistent behavior on duplicate semantic codes with DELAS parser, error messages are displayed by DELAC parser, instead of silently ignoring the duplicate code.

@martinec martinec closed this in 89940db Apr 7, 2016

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment