Loading ...
Sorry, an error occurred while loading the content.

Re: [linuxham] fldigi --wfall-only

Expand Messages
  • Ed
    That should be libfltk-dev. Sorry
    Message 1 of 14 , Feb 3, 2013
    • 0 Attachment
      That should be libfltk-dev. Sorry
    • Darren Long
      Ah interesting: darren@len:~$ sudo apt-get install libfltk-dev Reading package lists... Done Building dependency tree Reading state information... Done Package
      Message 2 of 14 , Feb 3, 2013
      • 0 Attachment
        Ah interesting:

        darren@len:~$ sudo apt-get install libfltk-dev
        Reading package lists... Done
        Building dependency tree
        Reading state information... Done
        Package libfltk-dev is a virtual package provided by:
        libfltk1.3-dev 1.3.0-8
        libfltk1.1-dev 1.1.10-14
        You should explicitly select one to install.


        Darren, G0HWW

        On 03/02/13 14:23, Ed wrote:
        > That should be libfltk-dev. Sorry
        >
      • Darren Long
        Oh. Not interesting at all. libfltk1.3-dev was already installed, I was just being silly. On to the debug build. Darren
        Message 3 of 14 , Feb 3, 2013
        • 0 Attachment
          Oh. Not interesting at all. libfltk1.3-dev was already installed, I was
          just being silly. On to the debug build.

          Darren

          On 03/02/13 14:40, Darren Long wrote:
          > Ah interesting:
          >
          > darren@len:~$ sudo apt-get install libfltk-dev
          > Reading package lists... Done
          > Building dependency tree
          > Reading state information... Done
          > Package libfltk-dev is a virtual package provided by:
          > libfltk1.3-dev 1.3.0-8
          > libfltk1.1-dev 1.1.10-14
          > You should explicitly select one to install.
          >
          >
          > Darren, G0HWW
          >
          > On 03/02/13 14:23, Ed wrote:
          >> That should be libfltk-dev. Sorry
          >>
          >
        • Ed
          ... Remove the 1.1 version. Ed
          Message 4 of 14 , Feb 3, 2013
          • 0 Attachment
            On 02/03/2013 09:40 AM, Darren Long wrote:
            > Ah interesting:
            >
            > darren@len:~$ sudo apt-get install libfltk-dev
            > Reading package lists... Done
            > Building dependency tree
            > Reading state information... Done
            > Package libfltk-dev is a virtual package provided by:
            > libfltk1.3-dev 1.3.0-8
            > libfltk1.1-dev 1.1.10-14
            > You should explicitly select one to install.
            >
            >
            > Darren, G0HWW
            >
            > On 03/02/13 14:23, Ed wrote:
            >> That should be libfltk-dev. Sorry
            >>
            >
            >

            Remove the 1.1 version.

            Ed
          • Ed
            ... I build fltk from source. Just because Ubuntu, all flavors, insist on having both versions. fldigi wants to see 1.3 Ed W3NR
            Message 5 of 14 , Feb 3, 2013
            • 0 Attachment
              On 02/03/2013 09:43 AM, Darren Long wrote:
              > Oh. Not interesting at all. libfltk1.3-dev was already installed, I was
              > just being silly. On to the debug build.
              >
              > Darren

              I build fltk from source. Just because Ubuntu, all flavors, insist on
              having both versions. fldigi wants to see 1.3

              Ed W3NR
            • Darren Long
              Some results from gdb. It seems that having Text Capture enabled is the culprit. If I disable that, wfall-only works fine. The back trace shows a null this
              Message 6 of 14 , Feb 3, 2013
              • 0 Attachment
                Some results from gdb. It seems that having Text Capture enabled is the
                culprit. If I disable that, wfall-only works fine. The back trace
                shows a null this pointer which is bound to cause disappointment.
                Debugger output below.

                Darren, G0HWW

                Program received signal SIGSEGV, Segmentation fault.
                0x00000000006c6026 in cLogfile::log_to_file (this=0x0,
                type=cLogfile::LOG_RX, s=...) at misc/log.cxx:63
                63 if (!logfile || ferror(logfile) || s.empty())
                (gdb) bt
                #0 0x00000000006c6026 in cLogfile::log_to_file (this=0x0,
                type=cLogfile::LOG_RX, s=...) at misc/log.cxx:63
                #1 0x000000000061ba20 in display_rx_data (data=114 'r', style=0) at
                dialogs/fl_digi.cxx:6101
                #2 0x000000000061bb48 in rx_parser (data=114 'r', style=0) at
                dialogs/fl_digi.cxx:6131
                #3 0x000000000061bdb7 in put_rx_char_flmain (data=114, style=0) at
                dialogs/fl_digi.cxx:6193
                #4 0x00000000006249e8 in std::tr1::_Bind<void (*(unsigned int,
                int))(unsigned int, int)>::__call<, 0, 1>(std::tr1::tuple<> const&,
                std::tr1::_Index_tuple<0, 1>) (
                this=0x7fffef105198, __args=...) at
                /usr/include/c++/4.7/tr1/functional:1179
                #5 0x0000000000622a6e in std::tr1::_Bind<void (*(unsigned int,
                int))(unsigned int, int)>::operator()<>() (this=0x7fffef105198)
                at /usr/include/c++/4.7/tr1/functional:1233
                #6 0x00000000006297b5 in func_wrap<std::tr1::_Bind<void (*(unsigned
                int, int))(unsigned int, int)> >::destroy(bool) (this=0x7fffef105190,
                run=true)
                at ./qrunner/fqueue.h:48
                #7 0x0000000000719f33 in fqueue::pop (this=0xbafa60, exec=true) at
                qrunner/fqueue.h:96
                #8 0x0000000000719f71 in fqueue::execute (this=0xbafa60) at
                qrunner/fqueue.h:102
                #9 0x0000000000719db8 in qrunner::execute (fd=7, arg=0xbafa40) at
                qrunner/qrunner.cxx:107
                #10 0x00007ffff74e0ac0 in fl_wait(double) () from
                /usr/lib/x86_64-linux-gnu/libfltk.so.1.3
                #11 0x00007ffff748a7b0 in Fl::wait(double) () from
                /usr/lib/x86_64-linux-gnu/libfltk.so.1.3
                #12 0x00007ffff748a91d in Fl::run() () from
                /usr/lib/x86_64-linux-gnu/libfltk.so.1.3
                #13 0x0000000000681cd1 in main (argc=2, argv=0x7fffffffe0a8) at main.cxx:533


                On 03/02/13 14:48, Ed wrote:
                > On 02/03/2013 09:40 AM, Darren Long wrote:
                >> Ah interesting:
                >>
                >> darren@len:~$ sudo apt-get install libfltk-dev
                >> Reading package lists... Done
                >> Building dependency tree
                >> Reading state information... Done
                >> Package libfltk-dev is a virtual package provided by:
                >> libfltk1.3-dev 1.3.0-8
                >> libfltk1.1-dev 1.1.10-14
                >> You should explicitly select one to install.
                >>
                >>
                >> Darren, G0HWW
                >>
                >> On 03/02/13 14:23, Ed wrote:
                >>> That should be libfltk-dev. Sorry
                >>>
                >>
                > Remove the 1.1 version.
                >
                > Ed
                >
              • Ed
                ... Repeatable here. Fixing it will give Dave something to do...hi. Thanks Darren. Ed W3NR
                Message 7 of 14 , Feb 3, 2013
                • 0 Attachment
                  On 02/03/2013 09:57 AM, Darren Long wrote:
                  > Some results from gdb. It seems that having Text Capture enabled is the
                  > culprit. If I disable that, wfall-only works fine. The back trace
                  > shows a null this pointer which is bound to cause disappointment.
                  > Debugger output below.
                  >
                  > Darren, G0HWW

                  Repeatable here. Fixing it will give Dave something to do...hi. Thanks
                  Darren.

                  Ed W3NR
                • John Phelps
                  Hi All, Found a possible bugfix for the waterfall-only mode crashing issue. (files attached) Works well here in testing. Attached is both a patch/fix and
                  Message 8 of 14 , Feb 3, 2013
                  Hi All,

                  Found a possible bugfix for the waterfall-only mode crashing issue. (files attached)
                  Works well here in testing.
                  Attached is both a patch/fix and screenshot of my debugger window (showing error and justifying why fix was placed here in program-flow)

                  My only question is: Do users want or need the Rx stream processed in waterfall-only mode?
                  ... guess I am asking for the technical definition of how waterfall-only should waterfall-only mode be, hihi.


                  Summary of the fix/patch.
                  This disables all processing of Rx text while in --wfall-only mode

                  +++ b/src/dialogs/fl_digi.cxx
                  @@ -6142,6 +6142,9 @@ static void put_rx_char_flmain(unsigned int data, int style)
                   {
                    ENSURE_THREAD(FLMAIN_TID);
                   
                  + // If in Waterfall Only mode: skip all processing of Rx characters
                  + if (bWF_only) return;



                  ~ John Phelps 
                  kl4yfd



                • w1hkj
                  ... Thanks John ... I ll import your patch into both 3.21 and 3.22 branches. Waterfall only is supposed to be just that, but the text stream has to be
                  Message 9 of 14 , Feb 3, 2013
                  • 0 Attachment
                    On 02/03/2013 12:55 PM, John Phelps wrote:
                    Hi All,

                    Found a possible bugfix for the waterfall-only mode crashing issue. (files attached)
                    Works well here in testing.
                    Attached is both a patch/fix and screenshot of my debugger window (showing error and justifying why fix was placed here in program-flow)

                    My only question is: Do users want or need the Rx stream processed in waterfall-only mode?
                    ... guess I am asking for the technical definition of how waterfall-only should waterfall-only mode be, hihi.


                    Summary of the fix/patch.
                    This disables all processing of Rx text while in --wfall-only mode

                    +++ b/src/dialogs/fl_digi.cxx
                    @@ -6142,6 +6142,9 @@ static void put_rx_char_flmain(unsigned int data, int style)
                     {
                      ENSURE_THREAD(FLMAIN_TID);
                     
                    + // If in Waterfall Only mode: skip all processing of Rx characters
                    + if (bWF_only) return;



                    ~ John Phelps 
                    kl4yfd

                    Thanks John ... I'll import your patch into both 3.21 and 3.22 branches.

                    Waterfall only is supposed to be just that, but the text stream has to be available via the xmlrpc calls.

                    Dave
                  • w1hkj
                    JP almost had it right on the WF-only patch. Please apply this one to 3.21.67 to cure this seg fault. BTW, this is not a fault one would expect to encounter
                    Message 10 of 14 , Feb 3, 2013
                    • 1 Attachment
                    • 1 KB
                    JP almost had it right on the WF-only patch. Please apply this one to
                    3.21.67 to cure this seg fault.

                    BTW, this is not a fault one would expect to encounter unless:

                    You started fldigi in full screen mode.
                    Enabled the "File | Text capture | Log all RX/TX text" menu item
                    Exited fldigi

                    Started fldigi with the command line sequence "--wo" or "--waterfall-only"
                    Started decoding incoming data

                    Most users of the --wo command line switch are in MS world and use
                    ancillary programs to display the text, and other aspects of fldigi
                    operation. Those programs use fldigi as a modem engine with waterfall
                    display. They would rarely if ever have performed the above sequence of
                    operations.

                    73, Dave, W1HKJ
                  Your message has been successfully submitted and would be delivered to recipients shortly.