bug to watch for

[R. Torsten Clay]

Here is one bug I have known about for a while but haven't tracked down yet.

When running, you type a callsign and press enter. This send the exchange, opens
the exchange entry line, and moves the cursor to the exchange entry line.

Sometimes the program sends the exchange and opens the exchange entry line,
but doesn't move the cursor down. Pressing down arrow gets you in the right place.
I haven't figured out why this happens. It is very rare however, maybe once every 100
qso's.

Tor

[Nate Bargmann]

Interesting. I'll keep an eye out for it.

On a related note. How do you handle debugging? So far I've studied
the code path and made notes while figuring out the misbehavior. It
seems that trying to use QtCreator's debugging feature has failed to
load one of the libraries.

73, de Nate >>

--

"The optimist proclaims that we live in the best of all
possible worlds. The pessimist fears this is true."

Ham radio, Linux, bikes, and more: http://www.n0nb.us

[R. Torsten Clay]

For debugging I usually just insert qDebug lines to print stuff out. Pretty crude but
it has worked for me.

Tor

[Nate Bargmann]

* On 2012 18 Jun 08:47 -0500, R. Torsten Clay wrote:
> For debugging I usually just insert qDebug lines to print stuff out. Pretty
> crude but
> it has worked for me.

Sometimes crude is better! Essentially this is what I do when debugging
Hamlib by using calls to rig_debug() except when I introduce a bug that
segfaults...