Change in ...osmo-trx[master]: Transceiver: exit process when BTS drops connection

pespin gerrit-no-reply at
Mon Aug 26 13:53:53 UTC 2019

pespin has posted comments on this change. ( )

Change subject: Transceiver: exit process when BTS drops connection

Patch Set 2:

(1 comment)

> Patch Set 2: Code-Review-1
> (1 comment)
> > No, true means success and false means failure everywhere.
> Ok, nevermind. I was reading too quickly.
> I know you don't like C++ and its specific features, but I still think it makes more sense to use exceptions here. You can just catch them in *LoopAdapter() calls and terminate the process instead of spamming the code with dozens of `return true / false`.

No thanks, I'm not doing that. I already had to fix some nasty deadlocks related to pthreads, destructors and exception handlers (see 86be40b4eb762d5c12e8e3f7388ca9f254e77b36). 
File Transceiver52M/Transceiver.cpp: 
PS2, Line 1041: if (bi.idle)
              :     return true;
> Here you're changing the logic, so the IDLE indications would never be passed to trxd_send_burst_ind […]
Good catch. I was confused when doing the change because there was actually already a bug in return codes in pullRadioVector() when returning an idle frame. I'm fixing it in a commit prior to this one (pushing in a moment).

To view, visit
To unsubscribe, or for help writing mail filters, visit

Gerrit-Project: osmo-trx
Gerrit-Branch: master
Gerrit-Change-Id: I2ccbe3c17b39fb792ea7810f840235c348054d66
Gerrit-Change-Number: 15289
Gerrit-PatchSet: 2
Gerrit-Owner: pespin <pespin at>
Gerrit-Reviewer: Jenkins Builder
Gerrit-Reviewer: fixeria <axilirator at>
Gerrit-Reviewer: pespin <pespin at>
Gerrit-Comment-Date: Mon, 26 Aug 2019 13:53:53 +0000
Gerrit-HasComments: Yes
Gerrit-Has-Labels: No
Comment-In-Reply-To: fixeria <axilirator at>
Gerrit-MessageType: comment
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <>

More information about the gerrit-log mailing list