-
-
Notifications
You must be signed in to change notification settings - Fork 30
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
[BUG] Flaky SEGFAULT while testing exec_command
#57
Open
Comments
webknjaz
changed the title
Flaky SEGFAULT while testing
[BUG] Flaky SEGFAULT while testing Jun 1, 2020
exec_command
exec_command
Fixed by PR #60 |
More segfaults appeared recently under both macos and ubuntu: |
ganeshrn
added a commit
to ganeshrn/pylibssh
that referenced
this issue
Jul 11, 2020
Fixes ansible#57 Fixes ansible#56 * Use channel created with Channel class instead of creating a new channel with exec_command()
Merged
ganeshrn
added a commit
to ganeshrn/pylibssh
that referenced
this issue
Jul 13, 2020
Fixes ansible#57 Fixes ansible#56 * Use channel created with Channel class instead of creating a new channel with exec_command()
This was
linked to
pull requests
Jul 30, 2020
Merged
This comment was marked as outdated.
This comment was marked as outdated.
Jakuje
added a commit
to Jakuje/pylibssh
that referenced
this issue
Nov 14, 2024
Fixes ansible#57 Signed-off-by: Jakub Jelen <[email protected]>
Jakuje
added a commit
to Jakuje/pylibssh
that referenced
this issue
Nov 14, 2024
Jakuje
added a commit
to Jakuje/pylibssh
that referenced
this issue
Nov 14, 2024
Fixes ansible#57 Signed-off-by: Jakub Jelen <[email protected]>
Jakuje
added a commit
to Jakuje/pylibssh
that referenced
this issue
Nov 14, 2024
Signed-off-by: Jakub Jelen <[email protected]>
Jakuje
added a commit
to Jakuje/pylibssh
that referenced
this issue
Nov 14, 2024
Fixes ansible#57 Signed-off-by: Jakub Jelen <[email protected]>
Jakuje
added a commit
to Jakuje/pylibssh
that referenced
this issue
Nov 14, 2024
Signed-off-by: Jakub Jelen <[email protected]>
Jakuje
added a commit
to Jakuje/pylibssh
that referenced
this issue
Nov 15, 2024
Signed-off-by: Jakub Jelen <[email protected]>
Jakuje
added a commit
to Jakuje/pylibssh
that referenced
this issue
Nov 15, 2024
Signed-off-by: Jakub Jelen <[email protected]>
Jakuje
added a commit
to Jakuje/pylibssh
that referenced
this issue
Nov 19, 2024
Fixes ansible#57 Signed-off-by: Jakub Jelen <[email protected]>
Jakuje
added a commit
to Jakuje/pylibssh
that referenced
this issue
Nov 19, 2024
Signed-off-by: Jakub Jelen <[email protected]>
Jakuje
added a commit
to Jakuje/pylibssh
that referenced
this issue
Nov 20, 2024
Fixes ansible#57 Signed-off-by: Jakub Jelen <[email protected]>
Jakuje
added a commit
to Jakuje/pylibssh
that referenced
this issue
Nov 20, 2024
Signed-off-by: Jakub Jelen <[email protected]>
Jakuje
added a commit
to Jakuje/pylibssh
that referenced
this issue
Nov 20, 2024
Fixes ansible#57 Signed-off-by: Jakub Jelen <[email protected]>
Jakuje
added a commit
to Jakuje/pylibssh
that referenced
this issue
Nov 20, 2024
Signed-off-by: Jakub Jelen <[email protected]>
Jakuje
added a commit
to Jakuje/pylibssh
that referenced
this issue
Nov 20, 2024
Fixes ansible#57 Signed-off-by: Jakub Jelen <[email protected]>
Jakuje
added a commit
to Jakuje/pylibssh
that referenced
this issue
Nov 20, 2024
Signed-off-by: Jakub Jelen <[email protected]>
Jakuje
added a commit
to Jakuje/pylibssh
that referenced
this issue
Nov 20, 2024
Previously, stack-local variables hold the callbacks. This worked as long as the call stack was not overridden by other function calls or as long as the server closed the channel very early. In other cases, the delayed close in libssh could result in calling the callbacks even after we believed the channel was freed, causing invalid memory access and crashes. Fixes ansible#57 Signed-off-by: Jakub Jelen <[email protected]>
Jakuje
added a commit
to Jakuje/pylibssh
that referenced
this issue
Nov 20, 2024
Removes the failed marker as it works now, as well as the forked fixture as it makes it hard to debug possible issues. Signed-off-by: Jakub Jelen <[email protected]>
Jakuje
added a commit
to Jakuje/pylibssh
that referenced
this issue
Nov 20, 2024
Previously, stack-local variables hold the callbacks. This worked as long as the call stack was not overridden by other function calls or as long as the server closed the channel very early. In other cases, the delayed close in libssh could result in calling the callbacks even after we believed the channel was freed, causing invalid memory access and crashes. Fixes ansible#57 Signed-off-by: Jakub Jelen <[email protected]>
Jakuje
added a commit
to Jakuje/pylibssh
that referenced
this issue
Nov 20, 2024
Removes the failed marker as it works now. Signed-off-by: Jakub Jelen <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
https://github.com/ansible/pylibssh/runs/725098816?check_suite_focus=true#step:10:146:
The text was updated successfully, but these errors were encountered: