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

Segment fault on file2brl -l <filename> #19

Open
larsbjorndal opened this issue Jan 26, 2016 · 2 comments
Open

Segment fault on file2brl -l <filename> #19

larsbjorndal opened this issue Jan 26, 2016 · 2 comments
Labels

Comments

@larsbjorndal
Copy link

When using the command: 'file2brl -l ',
I get a message about memory segment fault, and in parenthesis, (core
dumped).

@egli
Copy link
Member

egli commented Jan 26, 2016

It seems to dump core in https://github.com/liblouis/liblouisutdml/blob/master/tools/file2brl.c#L200 when doing essentially a strcpy(to, NULL) as lbu_getWriteablePath() presumably returns null.

Once the config file is read writeablePathPtr is set and the next
strcpy (tempFileName, lbu_getWriteablePath ());
on line 223 will work just fine.

Anyway the code in line 198 seems wrong.

@larsbjorndal can you try to invoke file2brl with -w. That should work, before we properly fix this issue.

@larsbjorndal
Copy link
Author

larsbjorndal commented Jan 26, 2016

Hi, Christian!

can you try to invoke file2brl with -w. That should
work, before we properly fix this issue.

Yes, 'file2brl -w . -l ' works. But the resulting file2brl.log is preceeded by a period, e.g. the path to writable directory specified with the -w . option. That's another error, I think.

Thank you and regards, Lars

@egli egli added the bug label Mar 14, 2017
@egli egli changed the title File2brl -l <filename> Segment fault on file2brl -l <filename> Mar 14, 2017
@egli egli changed the title Segment fault on file2brl -l <filename> Segment fault on file2brl -l <filename> Mar 14, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants