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

AppInspector errors when trying to set output filetype as HTML #75

Closed
localacct opened this issue Jan 20, 2020 · 1 comment
Closed

AppInspector errors when trying to set output filetype as HTML #75

localacct opened this issue Jan 20, 2020 · 1 comment

Comments

@localacct
Copy link

localacct commented Jan 20, 2020

Describe the bug
When trying to output the file as html, I will see that AppInspector tries looking for a non existent file "html/index.html" inside the current folder where the command is run.

Command line

dotnet /path/to/AppInspector.dll analyze -s file.c -f html

Error message in log.txt

Runtime error: Could not find a part of the path "/current/path/to/source/code/files/html/index.html"

If I tried the following, I see another error message

dotnet /path/to/AppInspector.dll analyze -s file.c -f html -o ./output.html

Error message in log.txt

Runtime error: Object reference not set to an instance of an object

To Reproduce
Try to analyze a file and select the filetype as html and use either of the command line arguments listed above. There are no issues setting the output filetype as JSON or Text.

Expected behavior
AppInspector should be able to output a proper html file

Screenshots

Desktop (please complete the following information):

  • OS: Mac OS 10.14.6 Mojave
  • Browser Google Chrome
  • Version 79.0.3945.117

Smartphone (please complete the following information):

Additional context

@guyacosta
Copy link
Contributor

Verified. The tool doesn't expect an output or -o argument for the html format since the file is managed by the tool itself. I've fixed it as follows: if an output parameter is specified for the html format the user will see a warning that the -o argument will be ignored for the html format type as designed. To see the HTML output -don't include an output argument. For json or text formats the -o is applicable and the output can be directed as desired. A fix to check for this non-working combination has been added and the next build will have the fix.

guyacosta pushed a commit that referenced this issue Jan 21, 2020
guyacosta added a commit that referenced this issue Jan 21, 2020
guyacosta pushed a commit that referenced this issue Jan 21, 2020
…irectory on linux. Minor tag name improvement for C library use.
guyacosta added a commit that referenced this issue Jan 21, 2020
Resolves issue #75 for path issues when run outside of app
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

2 participants