<div dir="ltr"><div dir="ltr"><div>Thanks, Dan :-)</div><div>I have progressed slightly beyond that point. I debugged most of the code using chirpc instead of chirpw. That let me use pdb, since chirpc did not have the threading problem. I then installed the Eric6 IDE, which did do a fairly good job of debugging chirpw with threads.</div><div><br></div><div>But there are also some fairly fundamental things I did not know about. such as the 'browser" tab in the CHIRP GUI.</div><div><br></div><div>In any event I hope to finish up my ft4 driver in the next few days.</div><div><br></div><div>I still have not figured out how to use the tox unit testing system.</div><div><br></div><div> I am uncertain about the semantics of the tone modes. In particuar the CHIRP code defines a mode (TSQL-R) that is not described on the web page <a href="https://chirp.danplanet.com/projects/chirp/wiki/DevelopersToneModes">https://chirp.danplanet.com/projects/chirp/wiki/DevelopersToneModes</a></div><div>but which appears to be the same asone of the cross modes.<br></div></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Thu, Jan 31, 2019 at 11:04 AM Dan Smith via chirp_devel <<a href="mailto:chirp_devel@intrepid.danplanet.com">chirp_devel@intrepid.danplanet.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">> I am a very experienced software developer, but not with CHIRP, or Python, or Ham radio, so I'm basically a newbie here. I have written a new driver for the FT-4XR and (eventually) for its siblings. The module successfully reads the radio, but then fails to fill in the GUI memory structures. I tried to use pdb as described at<br>
> <a href="https://docs.python.org/2/library/pdb.html" rel="noreferrer" target="_blank">https://docs.python.org/2/library/pdb.html</a><br>
> by inserting the following line at a point in my module:<br>
> import pdb; pdb.set_trace()<br>
> The breakpoint is reached, the line after mhy breakpoint is printed, and the (Pdb) prompt is shown on the console, but I cannot then type in a pdb command: characters are not shown on the console when typed and there is no evidence that the commands are being executed.<br>
<br>
This is probably because the driver is running in a different thread than the one that has control of the console (maybe?).<br>
<br>
> So, how do you guys debug? What am I doing wrong?<br>
<br>
With LOG.debug() statements :)<br>
<br>
I'm not a big debugger user myself, so perhaps I'm not the best person to help you with a workaround if you really need to figure out a way to use PBD with chirp.<br>
<br>
--Dan<br>
<br>
_______________________________________________<br>
chirp_devel mailing list<br>
<a href="mailto:chirp_devel@intrepid.danplanet.com" target="_blank">chirp_devel@intrepid.danplanet.com</a><br>
<a href="http://intrepid.danplanet.com/mailman/listinfo/chirp_devel" rel="noreferrer" target="_blank">http://intrepid.danplanet.com/mailman/listinfo/chirp_devel</a><br>
Developer docs: <a href="http://chirp.danplanet.com/projects/chirp/wiki/Developers" rel="noreferrer" target="_blank">http://chirp.danplanet.com/projects/chirp/wiki/Developers</a><br>
</blockquote></div>