pdb: fix SIGABRT in case of too long uris

[lbalaceanu]

buf in pdb_msg_dbg should correctly accomodate for pdb_bdy size
pdb_hdr + pdb_bdy should add to pdb_hdr.length (max 255)

Pre-Submission Checklist

• Commit message has the format required by CONTRIBUTING guide
• Commits are split per component (core, individual modules, libs, utils, ...)
• Each component has a single commit (if not, squash them into one commit)
• No commits to README files for modules (changes must be done to docbook files
  in doc/ subfolder, the README file is autogenerated)

Type Of Change

• [x ] Small bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds new functionality)
• Breaking change (fix or feature that would change existing functionality)

Checklist:

• [x ] PR should be backported to stable branches
• [x ] Tested changes locally
• Related to issue #XXXX (replace XXXX with an open issue number)

Description

Can I also port this back to 4.4? Thank you.

[miconda]

It can be merged and back ported to stable branches.

There is no restriction to back port to older branches, so you can push it to 4.4 as well -- the last two stable branches (now 5.0 and 5.1) are officially maintained from the perspective of doing releases out of them and it is not a must to backport. But if a developer wants to push to older versions, it is ok.

[lbalaceanu]

Thank you.