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.

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

SIGSEGV on OSX when compiling #31

Open
ghostwheel opened this issue Sep 22, 2018 · 0 comments
Open

SIGSEGV on OSX when compiling #31

ghostwheel opened this issue Sep 22, 2018 · 0 comments

Comments

@ghostwheel
Copy link

ghostwheel commented Sep 22, 2018

When lit is compiling as well as weaving, I get SIGSEGV.
Top of my file is:

@code_type c++ .cpp
@comment_type // %s
@Compiler lit -t main3.lit && g++ -c main3.cpp

It has compile errors. When I run lit -c, I get

'lit -c main3.lit' terminated by signal SIGSEGV (Address boundary error)

I think this is because the compiler outputs lines that lit can not process.
This is in main.lit:

        auto matches = matchFirst(line, r);

        string linenum = matches["linenum"];
        string fname = matches["filename"];
        string message = matches["message"];

I think one needs to first check if matches is empty. For example, if I condition the rest with

if( !matches.empty ) {

I don't get SIGSEGV, lit exits normally. I'm not sure if the best is if or assert.

I thought D won't have these annoying SIGSEGV!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant