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

Segfault when using gethostbyname() after dmtcp_restart #1103

Open
Koishi-love opened this issue Mar 28, 2024 · 1 comment
Open

Segfault when using gethostbyname() after dmtcp_restart #1103

Koishi-love opened this issue Mar 28, 2024 · 1 comment

Comments

@Koishi-love
Copy link

Koishi-love commented Mar 28, 2024

I have 2 similar programs launched by dmtcp. Their JTRACE logs are almost same before
"
DMTCP will now try to remap this area in read/write mode as
private (zero pages), so that glibc will automatically
stop using NSCD or ask NSCD daemon for new shared area
"

The first program can be restarted correctly. It has one above log with "area.name = /var/db/nscd/passwd".
The second program can be restart but not correctly because of a segfault caused by gethostbyname(). I find that there is an extra log "area.name = /var/db/nscd/hosts" besides log "area.name = /var/db/nscd/passwd".

I want to know what habits will leads to the segfault.

Version: master, 3.0.0 release

glibc2.17

@Koishi-love
Copy link
Author

Then I modify /etc/nscd.conf to shut down "hosts". The second program can be restarted correctly, and the gethostbyname() won't give any segfault. This means that (at least) for glibc2.17 the nscd indeed make some errors after restoring.

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

1 participant