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/.

Harald Welte laforge at gnumonks.org
Tue May 10 11:32:17 UTC 2016


Hi Keith,

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?

What are you doing to build the software this way?  I think it is a
complete waste of screen real-estate and I would like to do somethign
about it.

Does anyone have an explanation for this?

-- 
- Harald Welte <laforge at gnumonks.org>           http://laforge.gnumonks.org/
============================================================================
"Privacy in residential applications is a desirable marketing option."
                                                  (ETSI EN 300 175-7 Ch. A6)



More information about the OpenBSC mailing list