<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[Topics tagged with debugging]]></title><description><![CDATA[A list of topics that have been tagged with debugging]]></description><link>http://community.onion.io/tags/debugging</link><generator>RSS for Node</generator><lastBuildDate>Tue, 09 Jun 2026 23:23:14 GMT</lastBuildDate><atom:link href="http://community.onion.io/tags/debugging.rss" rel="self" type="application/rss+xml"/><pubDate>Thu, 06 Mar 2025 11:35:06 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[How to debug python code?]]></title><description><![CDATA[Hi,
I never really found an alternative to just run the code directly on the Omega and use "standard" debugging techniques like "print". We try to work as follows:

Create a python script which can be mainly tested on the dev machine (PC, Linux, Mac...whatever you are working with)
Ensure a good logging mechanism in the script in order to be able to write debug infos into log file (always a good thing even once your in production and need to debug a device)
Once your script is done to 90%, finish debugging on device.

If you find a better solution, I'll be glad to ear from you :-).
Best,
]]></description><link>http://community.onion.io/topic/5097/how-to-debug-python-code</link><guid isPermaLink="true">http://community.onion.io/topic/5097/how-to-debug-python-code</guid><dc:creator><![CDATA[MK]]></dc:creator><pubDate>Thu, 06 Mar 2025 11:35:06 GMT</pubDate></item><item><title><![CDATA[How to debug?]]></title><description><![CDATA[@mawg You should see if it's possible to run GDB on your onion -- probably you'll want the Omega2 that has the most RAM, i.e. 2+.  GDB offers things like breakpoints, stack-trace, read variables, capture on fault, etc.
https://docs.onion.io/omega2-docs/c-compiler-on-omega.html
Midway down this page, there's description on how to install gdb.
]]></description><link>http://community.onion.io/topic/3728/how-to-debug</link><guid isPermaLink="true">http://community.onion.io/topic/3728/how-to-debug</guid><dc:creator><![CDATA[JP Norair]]></dc:creator><pubDate>Sun, 15 Sep 2019 17:43:02 GMT</pubDate></item><item><title><![CDATA[[RESOLVED] GDB package has not installed.]]></title><description><![CDATA[Many thanks all. The problem has been resolved!!! Details is below.
@crispyoz said in GDB package has not installed.:

I took a new Omega 2+, configured the wifi and ran opkg install gdb without issue, which tells me the issue is with your device.  Can you post your /etc/opkg/distfeed.conf.

Here is my list of file /etc/opkg/distfeed.conf It configuration is works!!!:
root@Omega-D913:~# cat /etc/opkg/distfeeds.conf
#src/gz reboot_core http://downloads.lede-project.org/releases/17.01-SNAPSHOT/targets/ramips/mt7688/packages
src/gz reboot_base http://downloads.openwrt.org/snapshots/packages/mipsel_24kc/base
#src/gz reboot_onion http://downloads.lede-project.org/releases/17.01-SNAPSHOT/packages/mipsel_24kc/onion
## src/gz reboot_luci http://downloads.lede-project.org/releases/17.01-SNAPSHOT/packages/mipsel_24kc/luci
src/gz reboot_packages http://downloads.openwrt.org/snapshots/packages/mipsel_24kc/packages
## src/gz reboot_routing http://downloads.lede-project.org/releases/17.01-SNAPSHOT/packages/mipsel_24kc/routing
## src/gz reboot_telephony http://downloads.lede-project.org/releases/17.01-SNAPSHOT/packages/mipsel_24kc/telephony
src/gz omega2_core http://repo.onion.io/omega2/packages/core
src/gz omega2_base http://repo.onion.io/omega2/packages/base
src/gz omega2_packages http://repo.onion.io/omega2/packages/packages
src/gz omega2_routing http://repo.onion.io/omega2/packages/routing
src/gz omega2_onion http://repo.onion.io/omega2/packages/onion


I can't help but comment that after 30 years writing C and ASM code, I consider gdb to always be a last resort. Logging is your friend,  search for my response on how to set up a remote logging server for your Omega. I have 80+ devices, all running my own custom applications, and there is nothing I need to know about these devices that I cannot understand using logging, or by listening on wireshark.

You are hero. Logging, asserts, tracing are good instruments, but I drop much time to find errors without Debugger. The debugger is more perfect instrument for me. And I'm codding in C++ - it's need powerfull IDE such as Visual Studio or Eclipse, because C++ syntax is too difficult for a simple text editor.
By the way. The problem was links with different versions of Kernel and Packages. Default repository downloading packages from the OpenWRT v. 19xx, but the Onion OS is based on version 18.06.
Now I'm installed gdb and gdbserver. Both of them are already tested and works! Subject can be closed.
]]></description><link>http://community.onion.io/topic/3692/resolved-gdb-package-has-not-installed</link><guid isPermaLink="true">http://community.onion.io/topic/3692/resolved-gdb-package-has-not-installed</guid><dc:creator><![CDATA[Modest Polykarpovich]]></dc:creator><pubDate>Fri, 30 Aug 2019 21:11:15 GMT</pubDate></item><item><title><![CDATA[Editor in the Onion Console -- left full of debugging code!]]></title><description><![CDATA[@György-Farkas said in Editor in the Onion Console -- left full of debugging code!:

There will be an upgraded Omega2(+) firmware release and/or a bug free official web-based Onion Console someday ...
@Silvia  you are too optimistic 

Oh well, I had to at least try! 
]]></description><link>http://community.onion.io/topic/2696/editor-in-the-onion-console-left-full-of-debugging-code</link><guid isPermaLink="true">http://community.onion.io/topic/2696/editor-in-the-onion-console-left-full-of-debugging-code</guid><dc:creator><![CDATA[Silvia]]></dc:creator><pubDate>Mon, 05 Feb 2018 12:40:10 GMT</pubDate></item><item><title><![CDATA[i2c device not visible by i2cdetect]]></title><description><![CDATA[@Kit-Bishop That is my understanding aswell, the Omega is already drawing around 200mA of current. So in effect he is trying to put the sensor in parallel with the Omega, power-wise.
If the OP has a breadboard PSU use that for the power otherwise use the Vout shown in the diagram.
]]></description><link>http://community.onion.io/topic/313/i2c-device-not-visible-by-i2cdetect</link><guid isPermaLink="true">http://community.onion.io/topic/313/i2c-device-not-visible-by-i2cdetect</guid><dc:creator><![CDATA[Sawyer McBride]]></dc:creator><pubDate>Wed, 23 Dec 2015 12:51:17 GMT</pubDate></item></channel></rss>