This is just to notify you that https://support.dcmtk.org/redmine/issues/373 still happens.
It happens in DcmTCPConnection::write() when the read-end of the DcmTransportConnection socket is closed. A write to that socket generates a SIGPIPE signal, which if unhandled will segfault the application.
The proposed fix in the original bug report seems valid.
Cheers,
Brandon
Bug #373
Moderator: Moderator Team
-
- OFFIS DICOM Team
- Posts: 1444
- Joined: Tue, 2004-11-02, 17:22
- Location: Oldenburg, Germany
- Contact:
Re: Bug #373
Thanks for the information. Your description of the condition under which the bug occurs should be precise enough to allow us to fix this. This will not make it into DCMTK 3.6.4, though, which is due for release in a couple of days.
Who is online
Users browsing this forum: Google [Bot] and 1 guest