Attention is currently required from: daniel, laforge, osmith, pespin.

neels has posted comments on this change by pespin. ( 
https://gerrit.osmocom.org/c/osmo-mgw/+/39224?usp=email )

Change subject: mgw: CRCX: Split mgcp header pars parsing into a previous step
......................................................................


Patch Set 9: Code-Review+2

(2 comments)

File src/libosmo-mgcp/mgcp_msg.c:

https://gerrit.osmocom.org/c/osmo-mgw/+/39224/comment/d9ca525b_c631163f?usp=email
 :
PS8, Line 39:   LOGP(DLMGCP, LEVEL, "endpoint:%s " FMT, (PDATA) ? 
((PDATA)->epname ? : "null-epname") : "null-pdata", ##ARGS)
> I wouldn't expect pdata to be null at any time but fine anyway.
i agree, but every so often i ended up with bugs with segfaults where a null 
log would have helped


File src/libosmo-mgcp/mgcp_protocol.c:

https://gerrit.osmocom.org/c/osmo-mgw/+/39224/comment/78646661_38a0b196?usp=email
 :
PS4, Line 710:  if (osmux_init(trunk) < 0) {
> That means making even more changes in this commit, so no, I'll keep it there 
> in here. […]
Done



--
To view, visit https://gerrit.osmocom.org/c/osmo-mgw/+/39224?usp=email
To unsubscribe, or for help writing mail filters, visit 
https://gerrit.osmocom.org/settings?usp=email

Gerrit-MessageType: comment
Gerrit-Project: osmo-mgw
Gerrit-Branch: master
Gerrit-Change-Id: I3ee5158c254213203830fe9c38de11c15b4b19c1
Gerrit-Change-Number: 39224
Gerrit-PatchSet: 9
Gerrit-Owner: pespin <[email protected]>
Gerrit-Reviewer: Jenkins Builder
Gerrit-Reviewer: daniel <[email protected]>
Gerrit-Reviewer: laforge <[email protected]>
Gerrit-Reviewer: neels <[email protected]>
Gerrit-Reviewer: osmith <[email protected]>
Gerrit-Reviewer: pespin <[email protected]>
Gerrit-Attention: osmith <[email protected]>
Gerrit-Attention: laforge <[email protected]>
Gerrit-Attention: pespin <[email protected]>
Gerrit-Attention: daniel <[email protected]>
Gerrit-Comment-Date: Tue, 21 Jan 2025 15:50:08 +0000
Gerrit-HasComments: Yes
Gerrit-Has-Labels: Yes
Comment-In-Reply-To: neels <[email protected]>
Comment-In-Reply-To: pespin <[email protected]>

Reply via email to