A.2.3. Message-based Transport_1 (&_2) fails to report a NACK (only prints MSG: MESSAGE_TOO_SHORT to stdout)

[GoogleCodeExporter]

What steps will reproduce the problem?
1.
2.
3.

What is the expected output? What do you see instead?

Please use labels and text to provide additional information.
A.2.3. Message-based Transport_4 (&_5) reports the wrong failure

Similar comments to A.2.3. Message-based Transport_1 (&_2); however RFC 4465 
states ‘DECOMPRESSION-FAILURE  MESSAGE_TOO_SHORT and the test reports ‘MSG: 
INVALID_CODE_LOCATION’ along with errors

***ERROR: function: "initStateless()"

file: "c:\users\abc\documents\myboghe_update_sigcomp_vs2010\tinysigcomp\src\tcom

p_message.c"

line: "170"

MSG: INVALID_CODE_LOCATION

***ERROR: function: "tcomp_decompressordisp_internalDecompress()"

file: "c:\users\abc\documents\myboghe_update_sigcomp_vs2010\tinysigcomp\src\tcom

p_decompressordisp.c"

line: "183"

MSG: Failed to create new sigcomp message.

xoutpout: NO

Original issue reported on code.google.com by boss...@yahoo.fr on 8 Jan 2013 at 11:39

[GoogleCodeExporter]

Original comment by boss...@yahoo.fr on 10 Jan 2013 at 11:28

• Changed state: NextRelease

[GoogleCodeExporter]

Issue 171 has been merged into this issue.

Original comment by boss...@yahoo.fr on 10 Jan 2013 at 11:31

[GoogleCodeExporter]

Fixed in SVN r805+
/!\Please note that some torture tests require previous ones and the first have 
to be started with clean manager state.

Original comment by boss...@yahoo.fr on 10 Jan 2013 at 12:46

• Changed state: Fixed