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

add configure script argument to workaround broken cuserid() function #42

Closed
shanedsnyder opened this issue May 13, 2021 · 3 comments
Closed

Comments

@shanedsnyder
Copy link
Contributor

In GitLab by @shanedsnyder on Sep 24, 2015, 16:25

We need a configure-time argument to work around cuserid() segmentation faults by replacing that logic with getenv("LOGNAME"). I don't see a way to handle this at run time.

@shanedsnyder
Copy link
Contributor Author

In GitLab by @shanedsnyder on Sep 24, 2015, 16:25

Remember to document this in the Cray installation recipe as well.

@shanedsnyder
Copy link
Contributor Author

In GitLab by @shanedsnyder on Sep 24, 2015, 16:25

The first step is to update the runtime logic for determining user id, so that it tries each of cuserid(), getenv("LOGNAME"), and finally sprintf(..., getuid()). Testing on surveyor (BG/P) and VEAS (BG/Q) confirm that the LOGNAME environment variable is not set by default on those systems, so they will fall back directly to getuid() if cuserid() does not work.

The --disable-cuserid configure argument will activate ifdef wrappers around the cuserid() portion of the code.

@shanedsnyder
Copy link
Contributor Author

In GitLab by @shanedsnyder on Sep 24, 2015, 16:25

This is complete in svn now and tested on Beagle. The documentation for darshan-runtime has been updated accordingly.

shanedsnyder added a commit that referenced this issue Dec 1, 2022
these logs are moving to darshan-logs repo in PR #42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant