strange file names in log (was Re: Persistent Uplink activity from Moto KRZR K3)

This is merely a historical archive of years 2008-2021, before the migration to mailman3.

A maintained and still updated list archive can be found at https://lists.osmocom.org/hyperkitty/list/OpenBSC@lists.osmocom.org/.

Alexander Chemeris alexander.chemeris at gmail.com
Tue May 10 13:53:56 UTC 2016


On Tue, May 10, 2016 at 2:32 PM, Harald Welte <laforge at gnumonks.org> wrote:
> On Tue, May 10, 2016 at 11:01:26AM +0300, Alexander Chemeris wrote:
> > > <0000> ../../../../osmo-bts/src/common/rsl.c:1642
> > > (bts=0,trx=0,ts=0,ss=0) Handing RLL msg UNIT_DATA_IND from LAPDm to MEAS REP
>
> How did you manage to get the "../../../../" into the filename path?
> I've not seen this before, normally this just states "rsl.c" or maybe
> common/rsl.c but not the complete path?

This happens when you build in a directory outside of the source path
- e.g. we're doing this with the osmo-combo script which I think Keith
is using.

So yes, Holger is right.

-- 
Regards,
Alexander Chemeris.
CEO, Fairwaves, Inc.
https://fairwaves.co



More information about the OpenBSC mailing list