View Issue Details [ Jump to Notes ] | [ Print ] | ||||||||
ID | Project | Category | View Status | Date Submitted | Last Update | ||||
0005046 | ParaView | (No Category) | public | 2007-05-16 16:49 | 2007-05-22 12:56 | ||||
Reporter | David Karelitz | ||||||||
Assigned To | Utkarsh Ayachit | ||||||||
Priority | high | Severity | minor | Reproducibility | always | ||||
Status | closed | Resolution | fixed | ||||||
Platform | OS | OS Version | |||||||
Product Version | |||||||||
Target Version | Fixed in Version | ||||||||
Summary | 0005046: Windows --connect-id issue | ||||||||
Description | If you start the client listening for a connection on windows without the --connect-id flag, and then launch a linux server with the --connect-id flag, the client segfaults | ||||||||
Tags | No tags attached. | ||||||||
Project | |||||||||
Topic Name | |||||||||
Type | |||||||||
Attached Files | |||||||||
Relationships | |
Relationships |
Notes | |
(0007692) Utkarsh Ayachit (administrator) 2007-05-18 13:25 |
If the connection handshake failed, the process module was incorrectly firing connection created events which was confusing the client. Fixed that. /cvsroot/ParaView3/ParaView3/Servers/Common/vtkProcessModuleConnectionManager.cxx,v <-- vtkProcessModuleConnectionManager.cxx new revision: 1.19; previous revision: 1.18 |
Notes |
Issue History | |||
Date Modified | Username | Field | Change |
2011-06-16 13:10 | Zack Galbreath | Category | => (No Category) |
Issue History |
Copyright © 2000 - 2018 MantisBT Team |