Git Product home page Git Product logo

Comments (9)

tobiasbrunner avatar tobiasbrunner commented on May 24, 2024

It might not be entirely safe to use yytext (settings_parser_get_text in our case) in yyerror (settings_parser_error), especially in those test cases. But this doesn't seem like that much of an issue (anything but valgrind won't notice) and for some errors it could give the user a clearer indication what's wrong in the config file, so I'd rather keep it in.

from strongswan.

Thermi avatar Thermi commented on May 24, 2024

from strongswan.

tobiasbrunner avatar tobiasbrunner commented on May 24, 2024

So that's musl output? Not from valgrind? And where does it crash? (Seems to continue running after the first reports.)

from strongswan.

Thermi avatar Thermi commented on May 24, 2024

No, that's valgrind output, but I checked what exactly happened with valgrind. I can get you a complete coredump when it crashes in the test with all binaries involved, if you want.

EDIT: Also the log messages of valgrind might or might not be synchronized with the output of the binary that is run using valgrind.

from strongswan.

tobiasbrunner avatar tobiasbrunner commented on May 24, 2024

So which test cases crashes exactly?

from strongswan.

Thermi avatar Thermi commented on May 24, 2024

Running case 'valid/invalid data': +-
Failure in 'test_invalid': SIGSEGV(11) (i = 0)

from strongswan.

tobiasbrunner avatar tobiasbrunner commented on May 24, 2024

OK, yeah, when I run this test with TESTS_VERBOSITY=1 I see this:

syntax error, unexpected $end, expecting NAME or NEWLINE or '}' [�]

That's for this input

unterminated {
  not = valid

Since it reaches EOF, there is not really any incorrect text to report, so yytext and yyleng are not properly defined (the latter is still 1 even though the former points wherever). Unfortunately, it doesn't seem possible to distinguish between this case and others where the output could make sense (e.g. for spaces in name {}, where the error message is syntax error, unexpected NAME, expecting : or '{' or '=' [in] and [in] helps to identify where the problem is). So I guess we can't avoid removing that text output. I pushed that to the 346-parser-error branch. Let me know if it works for you.

from strongswan.

Thermi avatar Thermi commented on May 24, 2024

Thanks, with the patch it doesn't crash at the test anymore.

from strongswan.

tobiasbrunner avatar tobiasbrunner commented on May 24, 2024

Thanks for testing, applied to master.

from strongswan.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.