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

mbedit and mbnavedit don't properly handle input file format errors #1444

Open
tomoreilly opened this issue Mar 12, 2024 · 0 comments
Open

Comments

@tomoreilly
Copy link
Collaborator

Describe the bug
mbedit and mbnavedit don't handle input file format errors in a useful way. E.g. when specifying an ascii file named "junkFIle" on the command line:

mbedit -I junkFile : dialog says "Unable to open input file. You may not have permission in this directory!"
(stderr message is more useful: "Illegal format identifier, initialization failed")

mbnavedit -I junkFile: main app window is blank, with no error dialog or stderr message

To Reproduce
Create a small ascii file, e.g. named 'junk'. Provide junk as an input file to mbedit and mbnavedit.

Expected behavior
An error dialog message should appear, with appropriate message (e.g. "unreadable data in file 'junk'")

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