[PROTON-368] Calling pn_messenger_put with a message with no address causes a segmentation fault

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: proton-0.4
• Fix Version/s: proton-0.5
• Assignee: Rafael H. Schloming
• Reporter: Darryl Pierce
• Created: 26/Jul/13 15:02
• Updated: 07/Jan/16 11:33
• Resolved: 21/Aug/13 13:53

Description

In the Ruby bindings, if a Qpid::Proton::Message object is created but not given an address, and is then passed to Qpid::Proton::Messenger.put, the underlying C code blows up on the missing address.

Specifically at the line:

pn_link_t *sender = pn_messenger_target(messenger, address);

It should instead check that the address is set and, if not, fail earlier than this point.

Issue Links

• is duplicated by: PROTON-309 Messenger crashes if given a message that lacks a "to" address