Нотатки

1.Connect your iOS device to your Mac via USB. 2. Get the UDID for the connected device from iTunes or xcode organiser . 3.Open terminal in your Mac 4.type the following commands in the terminal $ ifconfig -l // First get the current list of interfaces. $ rvictl -s // Then run the tool with the UDID of the device. // This adds a new virtual network interface rvi0. $ ifconfig -l // Get the list of interfaces again, and you can see the new virtual network interface, rvi0, added by the previous command. $ sudo tcpdump -i rvi0 -w ./output.pcap // Get the traced packets and save it to a file Note : output.pacp is the packet traced file and will be located in the systems root directory When you're done you can stop the process with the following command. $ rvictl -x open the .pacp using wireshark and do your default procedures. Thats it !!!!!!!! No...

If you have application distributed through Apple appstore or Testflight you should be able to get automatic crash reports by opening XCode/Window/Organizer menu, then select app and go to Crashes tab. If crashes are not symbolicated you can symbolicate them manually by: 1. In organizer, call for context menu by pressing on crash log call stack section 2. Select "show in finder ..." menu item 3. Navigate up to ~/Library/Developer/Xcode/Products/ [app bundle id]/ [app version]/Crashes/Appstore/ 4. Copy debug symbols there: 5. Go back to Organizer and select "Resymbolicate" context menu item on call stack area. Now you should be able to see symbolicated log. Works for me on XCode 10 and Testflight.

https://en.wikipedia.org/wiki/Time_series_database RRDtool ( round-robin database tool ) aims to handle time series data such as network bandwidth , temperatures or CPU load. The data is stored in a circular buffer based database , thus the system storage footprint remains constant over time. https://en.wikipedia.org/wiki/RRDtool

To parse some text and extract matching items use:  $ echo " something " | egrep -o " regex "

To have Qt types in pretty shape in XCode lldb debugger use code from KDevelop project: Clone  git://anongit.kde.org/kdevelop command script import /Users/oomel/kdevelop/plugins/lldb/formatters/qt.py  Enjoy! This has to be done only once.

It is quite easy to capture infer info from qmake project: QMAKE_CXX = "infer capture --reactive -o /tmp/out -- $${QMAKE_CXX}" QMAKE_CC  = "infer capture --reactive -o /tmp/out -- $${QMAKE_CC}" Then you can run analysis on resulted data: $ infer analyze --reactive -o /tmp/out