-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
hey guys, in the op25 traffic pane, the thread that waits for new data to be received, waits to receive the pickled values for the fields in the traffic tab, can someone please tell me exactly where the thread gets its pickle from?? it is a c++ map right? the pickle i mean. does anyone know what file that comes from?
beucase i commented out the functions in the pickle.cc pickle.h, in op25/blocks/src/lib rebuilt same as stated on osmocom and i am still getting updated data in the python UI. how can this be??
is the pointer to that thread: gr_msg_queue_sptr d_msgq; i cant comment out anything in the snapshoit_du_handler beucase it wont biuld if i do. THanks! - -- - ------ Matt D - ------------
The code is not easy to follow and I'd hesitate to make definitive assertions about it, but the pickle data appears to originate from this code in hdu.cc
std::string hdu::snapshot() const { pickle p; p.add("duid", duid_str()); p.add("nac", nac_str()); p.add("mfid", mfid_str()); p.add("algid", algid_str()); p.add("kid", kid_str()); p.add("mi", mi_str()); p.add("tgid", tgid_str()); return p.to_string(); }
---In op25-dev@yahoogroups.com, op25-dev@yahoogroups.com wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
hey guys, in the op25 traffic pane, the thread that waits for new data to be received, waits to receive the pickled values for the fields in the traffic tab, can someone please tell me exactly where the thread gets its pickle from?? it is a c++ map right? the pickle i mean. does anyone know what file that comes from?
beucase i commented out the functions in the pickle.cc pickle.h, in op25/blocks/src/lib rebuilt same as stated on osmocom and i am still getting updated data in the python UI. how can this be??
is the pointer to that thread: gr_msg_queue_sptr d_msgq; i cant comment out anything in the snapshoit_du_handler beucase it wont biuld if i do. THanks! - -- - ------ Matt D - ------------
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 10/24/2013 09:39 AM, ikj1234i@yahoo.com wrote:
The code is not easy to follow and I'd hesitate to make definitive assertions about it, but the pickle data appears to originate from this code in hdu.cc
std::string hdu::snapshot() const { pickle p; p.add("duid", duid_str()); p.add("nac", nac_str()); p.add("mfid", mfid_str()); p.add("algid", algid_str()); p.add("kid", kid_str()); p.add("mi", mi_str()); p.add("tgid", tgid_str()); return p.to_string(); }
right i commented this out, rebiult and i still get the updates in the UI and the bad pointer error from the snapshot function. if indeed this is where the data originates, then there are two possiblities: (1) i am commenting out the code in a file that is not used at run time. i am unclear as to how this could be becuase i was under the impression that the source used by the program is in home/op25/blocks/src/lib which is where the script on osmo puts it and that is where i am doing the modifications; and (2) the second possibility is that the interpreter is still executing the commented out code, which seems pretty unlikely.
so lets say #1 from above is what is going on. where and how exactly can i make changes to the code??? or find out where the src files the program that is running are really biult from? im sorry if this is a super rookie question but . . . obviously i am stuck here.
Try running the following command to see if there is a version of op25 located in /usr/local
find /usr/local | grep op25
If there are file(s) found - use the 'ls -l' command to determine the file date(s) ls -l 'find /usr/local | grep op25` [note backticks]
Generally you must run 'make install' at the end of your build process which should update the relevant files within /usr/local/lib - if you're trying to run a local copy of these modules from your home directory you'd have to have set that up properly, I've not had experience with that
Max
---In op25-dev@yahoogroups.com, op25-dev@yahoogroups.com wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 10/24/2013 09:39 AM, ikj1234i@... mailto:ikj1234i@... wrote:
The code is not easy to follow and I'd hesitate to make definitive assertions about it, but the pickle data appears to originate from this code in hdu.cc
std::string hdu::snapshot() const { pickle p; p.add("duid", duid_str()); p.add("nac", nac_str()); p.add("mfid", mfid_str()); p.add("algid", algid_str()); p.add("kid", kid_str()); p.add("mi", mi_str()); p.add("tgid", tgid_str()); return p.to_string(); }
right i commented this out, rebiult and i still get the updates in the UI and the bad pointer error from the snapshot function. if indeed this is where the data originates, then there are two possiblities: (1) i am commenting out the code in a file that is not used at run time. i am unclear as to how this could be becuase i was under the impression that the source used by the program is in home/op25/blocks/src/lib which is where the script on osmo puts it and that is where i am doing the modifications; and (2) the second possibility is that the interpreter is still executing the commented out code, which seems pretty unlikely.
so lets say #1 from above is what is going on. where and how exactly can i make changes to the code??? or find out where the src files the program that is running are really biult from? im sorry if this is a super rookie question but . . . obviously i am stuck here.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 10/24/2013 01:07 PM, ikj1234i@yahoo.com wrote:
Try running the following command to see if there is a version of op25 located in /usr/local
find /usr/local | grep op25
If there are file(s) found - use the 'ls -l' command to determine the file date(s)
ls -l 'find /usr/local | grep op25` [note backticks]
Generally you must run 'make install' at the end of your build process which should update the relevant files within /usr/local/lib - if you're trying to run a local copy of these modules from your home directory you'd have to have set that up properly, I've not had experience with that
Max
thanks, yeah every-time i change some code i do:
./bootstrap && ./configure && make make check sudo make install
i did what you said above and i get:
matt@matt-Inspiron-1525:~$ find /usr/local | grep op25 /usr/local/include/gnuradio/op25_decoder_ff.h /usr/local/include/gnuradio/swig/op25.i /usr/local/share/gnuradio/grc/blocks/op25_traffic_pane.xml /usr/local/share/gnuradio/grc/blocks/op25_decoder.xml /usr/local/share/gnuradio/grc/blocks/op25_fsk4.xml /usr/local/share/gnuradio/grc/blocks/op25.xml /usr/local/lib/python2.7/dist-packages/gnuradio/op25.py /usr/local/lib/python2.7/dist-packages/gnuradio/op25_imbe.py /usr/local/lib/python2.7/dist-packages/gnuradio/op25.pyc /usr/local/lib/python2.7/dist-packages/gnuradio/op25.pyo /usr/local/lib/python2.7/dist-packages/gnuradio/_op25_imbe.la /usr/local/lib/python2.7/dist-packages/gnuradio/op25_imbe.pyc /usr/local/lib/python2.7/dist-packages/gnuradio/_op25.la /usr/local/lib/python2.7/dist-packages/gnuradio/_op25_imbe.so /usr/local/lib/python2.7/dist-packages/gnuradio/op25_imbe.pyo /usr/local/lib/python2.7/dist-packages/gnuradio/_op25.so /usr/local/lib/python2.7/dist-packages/baz/op25.py /usr/local/lib/python2.7/dist-packages/baz/op25_traffic_pane.pyc /usr/local/lib/python2.7/dist-packages/baz/op25_traffic_pane.py~ /usr/local/lib/python2.7/dist-packages/baz/op25.pyc /usr/local/lib/python2.7/dist-packages/baz/op25_traffic_pane.py /usr/local/lib/python2.7/dist-packages/baz/op25_traffic_pane.pyo /usr/local/lib/python2.7/dist-packages/baz/op25.pyo
matt@matt-Inspiron-1525:~$ ls -l 'find /usr/local | grep op25
and it just blinks at the prompt.
i dont know? what is this telling us ?
OK so when you compile and run 'make install' for the op25 software you now know where the compiled results get put. No idea what's going wrong for you, but note this 1) The directory from which you run 'make' (and its subdirectories such as src/lib etc) are where you should look to change source code such as .cc files or .h files 2) you should be able to grab a log of the compilation process and which files it's compiling etc 3) you should look at the timestamps of the files that get installed in /usr/local/lib to confirm they've been updated each time you recompile
Given that you apparently successfully compiled it the first time in order to install it, you should not have that much trouble recompiling ... In worst case as a test you can rm the file /usr/local/lib/python2.7/dist-packages/gnuradio/_op25.so. This should render your install inoperative until you re-install. The intent of the test is to prove that you're recompiling successfully.
Max
---In op25-dev@yahoogroups.com, op25-dev@yahoogroups.com wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 10/24/2013 01:07 PM, ikj1234i@... mailto:ikj1234i@... wrote:
Try running the following command to see if there is a version of op25 located in /usr/local
find /usr/local | grep op25
If there are file(s) found - use the 'ls -l' command to determine the file date(s)
ls -l 'find /usr/local | grep op25` [note backticks]
Generally you must run 'make install' at the end of your build process which should update the relevant files within /usr/local/lib - if you're trying to run a local copy of these modules from your home directory you'd have to have set that up properly, I've not had experience with that
Max
thanks, yeah every-time i change some code i do:
./bootstrap && ./configure && make make check sudo make install
i did what you said above and i get:
matt@matt-Inspiron-1525:~$ find /usr/local | grep op25 /usr/local/include/gnuradio/op25_decoder_ff.h /usr/local/include/gnuradio/swig/op25.i /usr/local/share/gnuradio/grc/blocks/op25_traffic_pane.xml /usr/local/share/gnuradio/grc/blocks/op25_decoder.xml /usr/local/share/gnuradio/grc/blocks/op25_fsk4.xml /usr/local/share/gnuradio/grc/blocks/op25.xml /usr/local/lib/python2.7/dist-packages/gnuradio/op25.py /usr/local/lib/python2.7/dist-packages/gnuradio/op25_imbe.py /usr/local/lib/python2.7/dist-packages/gnuradio/op25.pyc /usr/local/lib/python2.7/dist-packages/gnuradio/op25.pyo /usr/local/lib/python2.7/dist-packages/gnuradio/_op25_imbe.la /usr/local/lib/python2.7/dist-packages/gnuradio/op25_imbe.pyc /usr/local/lib/python2.7/dist-packages/gnuradio/_op25.la /usr/local/lib/python2.7/dist-packages/gnuradio/_op25_imbe.so /usr/local/lib/python2.7/dist-packages/gnuradio/op25_imbe.pyo /usr/local/lib/python2.7/dist-packages/gnuradio/_op25.so /usr/local/lib/python2.7/dist-packages/baz/op25.py /usr/local/lib/python2.7/dist-packages/baz/op25_traffic_pane.pyc /usr/local/lib/python2.7/dist-packages/baz/op25_traffic_pane.py~ /usr/local/lib/python2.7/dist-packages/baz/op25.pyc /usr/local/lib/python2.7/dist-packages/baz/op25_traffic_pane.py /usr/local/lib/python2.7/dist-packages/baz/op25_traffic_pane.pyo /usr/local/lib/python2.7/dist-packages/baz/op25.pyo
matt@matt-Inspiron-1525:~$ ls -l 'find /usr/local | grep op25
and it just blinks at the prompt.
i dont know? what is this telling us ?
Thanks a bunch Max. i had to uninstall everything and reinstall everything and now its back from the twilight zone.
On 10/24/2013 05:40 PM, ikj1234i@yahoo.com wrote:
OK so when you compile and run 'make install' for the op25 software you now know where the compiled results get put. No idea what's going wrong for you, but note this
- The directory from which you run 'make' (and its subdirectories such
as src/lib etc) are where you should look to change source code such as .cc files or .h files
- you should be able to grab a log of the compilation process and
which files it's compiling etc
- you should look at the timestamps of the files that get installed in
/usr/local/lib to confirm they've been updated each time you recompile
Given that you apparently successfully compiled it the first time in order to install it, you should not have that much trouble recompiling ... In worst case as a test you can rm the file /usr/local/lib/python2.7/dist-packages/gnuradio/_op25.so. This should render your install inoperative until you re-install. The intent of the test is to prove that you're recompiling successfully.
-
ikj1234i＠yahoo.com -
Matt D