-
Notifications
You must be signed in to change notification settings - Fork 255
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
recognize perfparser format (peek into file on open) #477
Labels
Comments
Rechecked now: we can check for perfparser file easily by inspecting the first bytes: $> xxd -l 12 my.perfparser
00000000: 5150 4552 4653 5452 4541 4d00 QPERFSTREAM. I have a look at implementing that using |
GitMensch
added a commit
to GitMensch/hotspot
that referenced
this issue
Oct 24, 2023
* check file open, providing nice and early error * explicit check for perfparser (magic number QPERFSTREAM) opening directly without the need to fall back to file name * explicit check for V1 perf data which isn't supported by perfparser * explicit check for unknown file type Fixes: KDAB#477
GitMensch
added a commit
to GitMensch/hotspot
that referenced
this issue
Oct 24, 2023
* check file open, providing nice and early error * explicit check for perfparser (magic number QPERFSTREAM) opening directly without the need to fall back to file name * explicit check for V1 perf data which isn't supported by perfparser * explicit check for unknown file type Fixes: KDAB#477
GitMensch
added a commit
to GitMensch/hotspot
that referenced
this issue
Oct 30, 2023
* check file open, providing nice and early error * explicit check for perfparser (magic number QPERFSTREAM) opening directly without the need to fall back to file name * explicit check for V1 perf data which isn't supported by perfparser * explicit check for unknown file type Fixes: KDAB#477
GitMensch
added a commit
to GitMensch/hotspot
that referenced
this issue
Nov 1, 2023
* check file open, providing nice and early error * explicit check for perfparser (magic number QPERFSTREAM) opening directly without the need to fall back to file name * explicit check for V1 perf data which isn't supported by perfparser * explicit check for unknown file type Fixes: KDAB#477
GitMensch
added a commit
to GitMensch/hotspot
that referenced
this issue
Nov 1, 2023
* check file open, providing nice and early error * explicit check for perfparser (magic number QPERFSTREAM) opening directly without the need to fall back to file name * explicit check for V1 perf data which isn't supported by perfparser * explicit check for unknown file type Fixes: KDAB#477
GitMensch
added a commit
to GitMensch/hotspot
that referenced
this issue
Nov 1, 2023
* check file open, providing nice and early error * explicit check for perfparser (magic number QPERFSTREAM) opening directly without the need to fall back to file name * explicit check for V1 perf data which isn't supported by perfparser * explicit check for unknown file type Fixes: KDAB#477
GitMensch
added a commit
to GitMensch/hotspot
that referenced
this issue
Nov 3, 2023
* check file open, providing nice and early error * explicit check for perfparser (magic number QPERFSTREAM) opening directly without the need to fall back to file name * explicit check for V1 perf data which isn't supported by perfparser * explicit check for unknown file type Fixes: KDAB#477
GitMensch
added a commit
to GitMensch/hotspot
that referenced
this issue
Nov 3, 2023
* check file open, providing nice and early error * explicit check for perfparser (magic number QPERFSTREAM) opening directly without the need to fall back to file name * explicit check for V1 perf data which isn't supported by perfparser * explicit check for unknown file type Fixes: KDAB#477
GitMensch
added a commit
to GitMensch/hotspot
that referenced
this issue
Nov 5, 2023
* check file open, providing nice and early error * explicit check for perfparser (magic number QPERFSTREAM) opening directly without the need to fall back to file name * explicit check for V1 perf data which isn't supported by perfparser * explicit check for unknown file type fixes KDAB#477
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is your feature request related to a problem? Please describe.
When naming a file something.perfparser (or even"banana") opening the file via hotspot does not work "The hotspot-perfparser binary existed with code 4 (invalid perf data file)."
Describe the solution you'd like
peek into the file specified at command line or via open dialog
Describe alternatives you've considered
Always remember to name the file correctly...
The text was updated successfully, but these errors were encountered: