Skip to content

Conversation

@ksco
Copy link
Collaborator

@ksco ksco commented Dec 23, 2025

No description provided.

#endif
}
printf_log(LOG_INFO, "Warning, context has been changed in Sigactionhanlder%s\n", (sigcontext->uc_mcontext.gregs[X64_RIP]!=sigcontext_copy.uc_mcontext.gregs[X64_RIP])?" (EIP changed)":"");
printf_log(LOG_DEBUG, "Warning, context has been changed in Sigactionhanlder%s\n", (sigcontext->uc_mcontext.gregs[X64_RIP] != sigcontext_copy.uc_mcontext.gregs[X64_RIP]) ? " (EIP changed)" : "");
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this one should stay at LOG_INFO, but the message is incomplete: it should mention that there is no jmpbuffer ready (and so the new RIP will not be satisfied)

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is the one repeated forever.

Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Then there is a real issue. This specific message is an error, not a warning.

Copy link
Owner

@ptitSeb ptitSeb Dec 23, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Those message appear when the signal should have be resumed using a siglongjmp, but the jumpbuffer is not available for some reason. This is not ok to continue.

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

Successfully merging this pull request may close these issues.

2 participants