Well, see above, it's the same. You can also login to xcache-00.t2.ucsd.edu and look at the core in /core/cores ... if you still remember how to get there ;)
Dumping memory at the address pResponse points to, I noticed in three cores string "[ERROR] Socket error", e.g.:
(gdb) x/48sb pResponse
0x7f7a84087e30: "\260\372\024\204z\177"
0x7f7a84087e37: ""
0x7f7a84087e38: "\024"
0x7f7a84087e3a: ""
0x7f7a84087e3b: ""
0x7f7a84087e3c: ""
0x7f7a84087e3d: ""
0x7f7a84087e3e: ""
0x7f7a84087e3f: ""
0x7f7a84087e40: "\377\377\377\377"
0x7f7a84087e45: ""
0x7f7a84087e46: ""
0x7f7a84087e47: ""
0x7f7a84087e48: "[ERROR] Socket error"
0x7f7a84087e5d: "\177"
...
Clearly, the pResponse has already been deallocated ... and apparently there was a socket error happening around that time.
Do you know of a way to nuke a specific socket? I could then run cache in valgrind and see what happens.
There is also this in Michal's list of things added for 4.9.1 (which worries me a bit at this point :) ):
b4307a8 [XrdCl] Remove unnecessary ref counting from MsgHandler
74ae6df [XrdCl] Remove unnecessary mutex.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.
{"api_version":"1.0","publisher":{"api_key":"05dde50f1d1a384dd78767c55493e4bb","name":"GitHub"},"entity":{"external_key":"github/xrootd/xrootd","title":"xrootd/xrootd","subtitle":"GitHub repository","main_image_url":"https://github.githubassets.com/images/email/message_cards/header.png","avatar_image_url":"https://github.githubassets.com/images/email/message_cards/avatar.png","action":{"name":"Open in GitHub","url":"https://github.com/xrootd/xrootd"}},"updates":{"snippets":[{"icon":"PERSON","message":"@osschar in #937: Well, see above, it's the same. You can also login to xcache-00.t2.ucsd.edu and look at the core in /core/cores ... if you still remember how to get there ;)\r\n\r\nDumping memory at the address pResponse points to, I noticed in three cores string \"[ERROR] Socket error\", e.g.:\r\n```\r\n(gdb) x/48sb pResponse\r\n0x7f7a84087e30: \"\\260\\372\\024\\204z\\177\"\r\n0x7f7a84087e37: \"\"\r\n0x7f7a84087e38: \"\\024\"\r\n0x7f7a84087e3a: \"\"\r\n0x7f7a84087e3b: \"\"\r\n0x7f7a84087e3c: \"\"\r\n0x7f7a84087e3d: \"\"\r\n0x7f7a84087e3e: \"\"\r\n0x7f7a84087e3f: \"\"\r\n0x7f7a84087e40: \"\\377\\377\\377\\377\"\r\n0x7f7a84087e45: \"\"\r\n0x7f7a84087e46: \"\"\r\n0x7f7a84087e47: \"\"\r\n0x7f7a84087e48: \"[ERROR] Socket error\"\r\n0x7f7a84087e5d: \"\\177\"\r\n...\r\n```\r\n\r\nClearly, the pResponse has already been deallocated ... and apparently there was a socket error happening around that time.\r\n\r\nDo you know of a way to nuke a specific socket? I could then run cache in valgrind and see what happens. \r\n\r\nThere is also this in Michal's list of things added for 4.9.1 (which worries me a bit at this point :) ):\r\nb4307a8 [XrdCl] Remove unnecessary ref counting from MsgHandler\r\n74ae6df [XrdCl] Remove unnecessary mutex."}],"action":{"name":"View Issue","url":"https://github.com/xrootd/xrootd/issues/937#issuecomment-475509867"}}}
[
{
"@context": "http://schema.org",
"@type": "EmailMessage",
"potentialAction": {
"@type": "ViewAction",
"target": "https://github.com/xrootd/xrootd/issues/937#issuecomment-475509867",
"url": "https://github.com/xrootd/xrootd/issues/937#issuecomment-475509867",
"name": "View Issue"
},
"description": "View this Issue on GitHub",
"publisher": {
"@type": "Organization",
"name": "GitHub",
"url": "https://github.com"
}
}
]
Use REPLY-ALL to reply to list
To unsubscribe from the XROOTD-DEV list, click the following link:
https://listserv.slac.stanford.edu/cgi-bin/wa?SUBED1=XROOTD-DEV&A=1
