-
Notifications
You must be signed in to change notification settings - Fork 3
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
Parse failure for specific log file #12
Comments
Looking at the prof file in jaspervdj/profiteur#22, it seems to be broken:
Look at the line 34160. There is no cost centre name in that line. Also |
BTW, maybe I should switch the ghc-prof parser from attoparsec to (mega)parsec or something for better error messages. Do you have any opinions to pick a parser library? |
It's coming from a ZIP file. It's the same as on my machine.
with GHC 8.2.2 (LTS 10.3) |
@maoe about parser library, I don't have opinions. |
@varosi Can you check if you can generate a broken .prof file again? If it's reproducible, I guess we should report it to GHC trac. In any case I'll probably give megaparsec a try for better error messages when I have time. |
Here is another one, but it seems that is opening fine: I think that if multiple processes try to create the same file - it could mess the file. In the perfect case they should wait one another or just use different (unique) file names and check if the file already exists. |
@varosi Thanks for checking. In that case you might want to use the -po option to distinguish processes. |
Thanks, but it is the same executable ran multiple times, i.e. all the processes have the same name, but different process id. |
Yeah I understand that. I mean, can you specify a unique identifier for each process using -po option at runtime? |
It's possible with redirecting via shell script, because currently the process is called from a application that we don't have control on. |
File and error reported here: jaspervdj/profiteur#22
I reproduced it using
ghc-prof
version1.4.0.4
The text was updated successfully, but these errors were encountered: