TCP address functions crash on error

Issue #213 closed

Paolo Brandoli repo owner created an issue 2018-02-09

The TCP functions that manage the address crash on error instead of returning an exception.

Comments (8)

Paolo Brandoli reporter
Addresses ~~#213~~. Added test for crashing TCPAddress functions

→ <<cset 73f3a13eab53e31cc49f37127f953f5cb80f0dd0>>
- 2018-02-12T20:46:31+00:00
Paolo Brandoli reporter
Addresses ~~#213~~. Corrected exception throwing on addresses functions

→ <<cset 2a4e688212e0df7218062e18e80f693667bd7ac2>>
- 2018-02-12T20:46:31+00:00
Paolo Brandoli reporter
Addresses ~~#213~~. Output error code for non expected tcp address exceptions

→ <<cset 10b5e339efe71ea7422cbf09e21f6171b08fa193>>
- 2018-02-12T22:54:47+00:00
Paolo Brandoli reporter
Addresses ~~#213~~. Updated tcp address test

→ <<cset 6acf366746479170edb0ae1b7e35440fdf62a094>>
- 2018-02-12T22:54:47+00:00
Paolo Brandoli reporter
Addresses ~~#213~~. Updated tcp address tests to catch the base exception (every platform throws something different)

→ <<cset fa3df74b8be5f5cc5f9ab4b69e6cad2ad4e36f54>>
- 2018-02-12T23:26:51+00:00
Paolo Brandoli reporter
Addresses ~~#213~~. Updated changes log.

→ <<cset d1b269abba67a0a88067fbcef000d1798dc4c605>>
- 2018-02-12T23:41:20+00:00
Paolo Brandoli reporter
- changed status to resolved
Resolves ~~#213~~ (TCP address functions crash on error) as per SOP FIXBUG/2

→ <<cset c77ca53cd110b338865036a57506d0af21f7fdcf>>
- 2018-02-12T23:41:20+00:00
Paolo Brandoli reporter
- changed status to closed
Closed in 4.1.1.1
- 2018-02-13T20:47:39+00:00
Log in to comment