You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When we try to analyze a core file that is generated from a script with a shebang or any other form of non-ELF file with executable permissions, Pystack will fail to analyze it because it will detect that the provided executable is not an ELF file (Executable and Linkable Format) and therefore it cannot be used to analyze the core file.
Expected Behavior
When Pystack detects that the provided file is not an ELF file, Pystack should analyze the core file that we provided in order to determine which Python executable to use. To properly analyze the core file, we can pass the full path to the executable that was used in the original invocation as the second argument to the pystack core command.
Is there an existing issue for this?
Current Behavior
When we try to analyze a core file that is generated from a script with a shebang or any other form of non-ELF file with executable permissions, Pystack will fail to analyze it because it will detect that the provided executable is not an ELF file (Executable and Linkable Format) and therefore it cannot be used to analyze the core file.
Expected Behavior
When Pystack detects that the provided file is not an ELF file, Pystack should analyze the core file that we provided in order to determine which Python executable to use. To properly analyze the core file, we can pass the full path to the executable that was used in the original invocation as the second argument to the
pystack core
command.$ pystack core $(COREFILE) /full/path/to/the/python/executable
Steps To Reproduce
To reproduce the issue generate a core file from a Python file with a shebang.
Pystack Version
1.3.0
Python Version
3.7, 3.8, 3.9, 3.10, 3.11, 3.12
Linux distribution
Debian, Ubuntu, Fedora, Red Hat, Arch Linux, Alpine Linux, Other
Anything else?
No response
The text was updated successfully, but these errors were encountered: