Skip to content
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

The SSH connection fails when pcre2 of the gcov version is used. #225

Closed
JetXujing opened this issue Apr 13, 2023 · 4 comments
Closed

The SSH connection fails when pcre2 of the gcov version is used. #225

JetXujing opened this issue Apr 13, 2023 · 4 comments

Comments

@JetXujing
Copy link
Contributor

JetXujing commented Apr 13, 2023

To reproduce the problem, perform the following steps:

  1. Add "-fprofile-arcs -ftest-coverage" option to CFLAGS.
  2. Compile and install pcre2.
  3. ssh connection in the new shell window.

According to the preceding steps, the SSH connection fails:
image

@zherczeg
Copy link
Collaborator

What is the point of this report? You added coverage info, installed the lib, ssh probably used it, gcc tried to write coverage info into root directory without permission, crash. This is nothing to do with the library.

@JetXujing
Copy link
Contributor Author

What I want to say is that adding coverage information should not affect pcre2 functions. According to the result, SSH directly or indirectly uses pcre2, and I am not sure whether the problem is caused by permission.

@zherczeg
Copy link
Collaborator

This repository is for pcre2 development. You modified the operation of the library. If you are not sure, the issue is not caused by your modification, don't report a bug.

Coverage collection usually (not always, sometimes it triggers compiler bugs, or cause timing issues) does not have side effects. However, the collected data is written back to the disk before exit, usually where the binary is. In your case, that is your /lib/something. It is normally write protected, so it cause a crash.

@JetXujing
Copy link
Contributor Author

Okay, I understand. Thank you.

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

No branches or pull requests

2 participants