You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
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.
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
The text was updated successfully, but these errors were encountered: