#77 exception trouble in nMessage constructor

[Manuel Moos]

When a short UDP packet is received and the
exception inside the nMessage constructor is thrown,
there's a memory leak and a fake assertion failure in
debug mode. Plus, the claim_id sent may be
considered part of the message (no exploits possible,
but a bug nontheless).

[Manuel Moos]

Logged In: YES
user_id=34808

I't not a memory leak after all; the data is held in a tArray
which will clear itself in the member destructor that's
automatically called. But the other problems are real.

[Manuel Moos]

Logged In: YES
user_id=34808

Small and ugly internal problem, postponed the fix to after
0.2.8.

[Manuel Moos]

Logged In: YES
user_id=34808

The claim_id problem is not real, either. It is removed from
the data that is to be turned into messages. The assertion
failure is fixed, referenceable objects with refcount zero are
allowed to delete themselves.

[Manuel Moos]

Logged In: YES
user_id=34808

The claim_id problem is not real, either. It is removed from
the data that is to be turned into messages. The assertion
failure is fixed, referenceable objects with refcount zero are
allowed to delete themselves.

[SourceForge Robot]

Logged In: YES
user_id=1312539

This Tracker item was closed automatically by the system. It was
previously set to a Pending status, and the original submitter
did not respond within 14 days (the time period specified by
the administrator of this Tracker).