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

i'm back with my flamp questions

Expand Messages
  • o11oo1oo
    Thought I had it after the build from source lesson, but tonight I saw this when trying to start it from a command line. terminate called after throwing an
    Message 1 of 15 , Oct 30, 2013
    • 0 Attachment
      Thought I had it after the build from source lesson, but tonight I saw this when trying to start it from a command line.

      terminate called after throwing an instance of 'SocketException'
        what():  getaddrinfo: 127.0.0.1 : 7322: Address family for hostname not supported

      I discovered that if the laptop was connected to the wifi router (as indicated by network-manager-applet "bars"), then flamp starts OK. Although by that time the test message i was trying to receive was gone.

      I found the help info about command line switches --arq-server-address (-port), --xmlrpc (etc.) but trying to start it with those tacked on the end doesnt seem to get me anywhere.

      Only other idea i could come up with is 'is this somehow related to port 7322 getting blocked by firewall settings? But that made no sense to me, if just connecting the wifi allows it to start.

      Do I need to edit those server-address and server-port settings into some file someplace?
    • o11oo1oo
      Do these messages I found in a log file mean anything to anybody here in regards to flamp failing to start unless i m connected to the internet? 12:52:30
      Message 2 of 15 , Nov 10, 2013
      • 0 Attachment

         Do these messages I found in a log file mean anything to anybody here in regards to flamp failing to start unless i'm connected to the internet?


        12:52:30 localhost abrt[1947]: Saved core dump of pid 1946 (/usr/local/bin/flamp) to /var/tmp/abrt/ccpp-2013-11-10-12:52:30-1946 (2011136 bytes)
        12:52:30 localhost abrtd: New client connected
        12:52:30 localhost abrt-server[1948]: Executable '/usr/local/bin/flamp' doesn't belong to any package and ProcessUnpackaged is set to 'no'
        12:52:30 localhost abrt-server[1948]: 'post-create' on '/var/tmp/abrt/ccpp-2013-11-10-12:52:30-1946' exited with 1
        12:52:30 localhost abrt-server[1948]: Deleting problem directory '/var/tmp/abrt/ccpp-2013-11-10-12:52:30-1946'


        "...doesn't belong to any package..." leapt out at me.

        Is there a way for me to set "ProcessUnpackaged" to 'yes'; and would that fix me up?



      • Robert Stiles
        Hello, Not being a Linux GURU I don t have an answer, but a quick search using google on this search term results in many hits. doesn t belong to any package
        Message 3 of 15 , Nov 10, 2013
        • 0 Attachment
          Hello, Not being a Linux GURU I don't have an answer, but a quick search using google on this search term results in many hits.

          doesn't belong to any package and ProcessUnpackaged is set to 'no'

          Robert, KK5VD


          From: "o11oo1oo@..." <o11oo1oo@...>
          To: linuxham@yahoogroups.com
          Sent: Sunday, November 10, 2013 1:06 PM
          Subject: [linuxham] RE: i'm back with my flamp questions

           
           Do these messages I found in a log file mean anything to anybody here in regards to flamp failing to start unless i'm connected to the internet?

          12:52:30 localhost abrt[1947]: Saved core dump of pid 1946 (/usr/local/bin/flamp) to /var/tmp/abrt/ccpp-2013-11-10-12:52:30-1946 (2011136 bytes)
          12:52:30 localhost abrtd: New client connected
          12:52:30 localhost abrt-server[1948]: Executable '/usr/local/bin/flamp' doesn't belong to any package and ProcessUnpackaged is set to 'no'
          12:52:30 localhost abrt-server[1948]: 'post-create' on '/var/tmp/abrt/ccpp-2013-11-10-12:52:30-1946' exited with 1
          12:52:30 localhost abrt-server[1948]: Deleting problem directory '/var/tmp/abrt/ccpp-2013-11-10-12:52:30-1946'

          "...doesn't belong to any package..." leapt out at me.
          Is there a way for me to set "ProcessUnpackaged" to 'yes'; and would that fix me up?




        • o11oo1oo
          well, i d done some searching, but guess i didnt stumble onto the answers yet. I did just find the answer to the ProcessUnpackaged... at github.com; got that
          Message 4 of 15 , Nov 10, 2013
          • 0 Attachment

             well, i'd done some searching, but guess i didnt stumble onto the answers yet.


            I did just find the answer to the 'ProcessUnpackaged...' at github.com; got that .conf file adjusted from 'no' to 'yes' but unfortunately still no joy starting flamp if my internet is not connected.



            ---In linuxham@yahoogroups.com, <kk5vd@...> wrote:

            Hello, Not being a Linux GURU I don't have an answer, but a quick search using google on this search term results in many hits.

            doesn't belong to any package and ProcessUnpackaged is set to 'no'

            Robert, KK5VD


            From: "o11oo1oo@..." <o11oo1oo@...>
            To: linuxham@yahoogroups.com
            Sent: Sunday, November 10, 2013 1:06 PM
            Subject: [linuxham] RE: i'm back with my flamp questions

             
             Do these messages I found in a log file mean anything to anybody here in regards to flamp failing to start unless i'm connected to the internet?

            12:52:30 localhost abrt[1947]: Saved core dump of pid 1946 (/usr/local/bin/flamp) to /var/tmp/abrt/ccpp-2013-11-10-12:52:30-1946 (2011136 bytes)
            12:52:30 localhost abrtd: New client connected
            12:52:30 localhost abrt-server[1948]: Executable '/usr/local/bin/flamp' doesn't belong to any package and ProcessUnpackaged is set to 'no'
            12:52:30 localhost abrt-server[1948]: 'post-create' on '/var/tmp/abrt/ccpp-2013-11-10-12:52:30-1946' exited with 1
            12:52:30 localhost abrt-server[1948]: Deleting problem directory '/var/tmp/abrt/ccpp-2013-11-10-12:52:30-1946'

            "...doesn't belong to any package..." leapt out at me.
            Is there a way for me to set "ProcessUnpackaged" to 'yes'; and would that fix me up?




          • David Ranch
            By any chance are you running FLamp on a 64bit OS? If so, this was a known issue on the last version of Flamp. Make sure you re running the newest version.
            Message 5 of 15 , Nov 10, 2013
            • 0 Attachment

              By any chance are you running FLamp on a 64bit OS?  If so, this was a known issue on the last version of Flamp.  Make sure you're running the newest version. 

              Beyond that, it looks like you're running a Fedora / RHEL / Centos box but the "post-create" on ... exited with 1" looks like a bug as there are lots of recent bug reports on that one.  You need to get the coredump to remain in /var/tmp/abrt/ccpp-* and once you can get there, running gdb against flamp and the core file should give us a backtrace to start troubleshooting things more.

              --David
              KI6ZHD



               Do these messages I found in a log file mean anything to anybody here in regards to flamp failing to start unless i'm connected to the internet?


              12:52:30 localhost abrt[1947]: Saved core dump of pid 1946 (/usr/local/bin/flamp) to /var/tmp/abrt/ccpp-2013-11-10-12:52:30-1946 (2011136 bytes)
              12:52:30 localhost abrtd: New client connected
              12:52:30 localhost abrt-server[1948]: Executable '/usr/local/bin/flamp' doesn't belong to any package and ProcessUnpackaged is set to 'no'
              12:52:30 localhost abrt-server[1948]: 'post-create' on '/var/tmp/abrt/ccpp-2013-11-10-12:52:30-1946' exited with 1
              12:52:30 localhost abrt-server[1948]: Deleting problem directory '/var/tmp/abrt/ccpp-2013-11-10-12:52:30-1946'


              "...doesn't belong to any package..." leapt out at me.

              Is there a way for me to set "ProcessUnpackaged" to 'yes'; and would that fix me up?




            • jhaynesatalumni
              I don t know much, but I think that stuff about ProcessUnpackaged means that the program you are running - flamp - was not installed from a package but rather
              Message 6 of 15 , Nov 11, 2013
              • 0 Attachment
                I don't know much, but I think that stuff about ProcessUnpackaged means that the program
                you are running - flamp - was not installed from a package but rather was installed by you
                compiling from source.  And that is all connected to the bug reporting machinery.

                what you could do is run the program under gdb by hand:

                script    (so everything you do here gets recorded in a file named typescript)
                gdb /usr/local/bin/flamp
                run
                (bunch of stuff gets printed - eventually program crashes)
                q   (for quit)
                bt  (for back trace)(or maybe I have those backwards)
                (eventually you ctrl-D to end the script session.  Then you can read the file typescript
                or send it to w1hkj for analysis)

                Jim W6JVE

                 



                ---In linuxham@yahoogroups.com, <o11oo1oo@...> wrote:

                 well, i'd done some searching, but guess i didnt stumble onto the answers yet.


                I did just find the answer to the 'ProcessUnpackaged...' at github.com; got that .conf file adjusted from 'no' to 'yes' but unfortunately still no joy starting flamp if my internet is not connected.



                ---In linuxham@yahoogroups.com, <kk5vd@...> wrote:

                Hello, Not being a Linux GURU I don't have an answer, but a quick search using google on this search term results in many hits.

                doesn't belong to any package and ProcessUnpackaged is set to 'no'

                Robert, KK5VD


                From: "o11oo1oo@..." <o11oo1oo@...>
                To: linuxham@yahoogroups.com
                Sent: Sunday, November 10, 2013 1:06 PM
                Subject: [linuxham] RE: i'm back with my flamp questions

                 
                 Do these messages I found in a log file mean anything to anybody here in regards to flamp failing to start unless i'm connected to the internet?

                12:52:30 localhost abrt[1947]: Saved core dump of pid 1946 (/usr/local/bin/flamp) to /var/tmp/abrt/ccpp-2013-11-10-12:52:30-1946 (2011136 bytes)
                12:52:30 localhost abrtd: New client connected
                12:52:30 localhost abrt-server[1948]: Executable '/usr/local/bin/flamp' doesn't belong to any package and ProcessUnpackaged is set to 'no'
                12:52:30 localhost abrt-server[1948]: 'post-create' on '/var/tmp/abrt/ccpp-2013-11-10-12:52:30-1946' exited with 1
                12:52:30 localhost abrt-server[1948]: Deleting problem directory '/var/tmp/abrt/ccpp-2013-11-10-12:52:30-1946'

                "...doesn't belong to any package..." leapt out at me.
                Is there a way for me to set "ProcessUnpackaged" to 'yes'; and would that fix me up?




              • o11oo1oo
                David, Jim, and all, I m still on Fedora 18 and it claims 32bits. The flamp ver is 2.1.01. I was unaware of gdb. Will definitely give that a shot. Thanks. Dan
                Message 7 of 15 , Nov 11, 2013
                • 0 Attachment

                  David, Jim, and all,


                  I'm still on Fedora 18 and it claims 32bits. The flamp ver is 2.1.01.


                  I was unaware of gdb. Will definitely give that a shot.


                  Thanks.


                  Dan



                  ---In linuxham@yahoogroups.com, <linuxham-fld@...> wrote:


                  By any chance are you running FLamp on a 64bit OS?  If so, this was a known issue on the last version of Flamp.  Make sure you're running the newest version. 

                  Beyond that, it looks like you're running a Fedora / RHEL / Centos box but the "post-create" on ... exited with 1" looks like a bug as there are lots of recent bug reports on that one.  You need to get the coredump to remain in /var/tmp/abrt/ccpp-* and once you can get there, running gdb against flamp and the core file should give us a backtrace to start troubleshooting things more.

                  --David
                  KI6ZHD



                   Do these messages I found in a log file mean anything to anybody here in regards to flamp failing to start unless i'm connected to the internet?


                  12:52:30 localhost abrt[1947]: Saved core dump of pid 1946 (/usr/local/bin/flamp) to /var/tmp/abrt/ccpp-2013-11-10-12:52:30-1946 (2011136 bytes)
                  12:52:30 localhost abrtd: New client connected
                  12:52:30 localhost abrt-server[1948]: Executable '/usr/local/bin/flamp' doesn't belong to any package and ProcessUnpackaged is set to 'no'
                  12:52:30 localhost abrt-server[1948]: 'post-create' on '/var/tmp/abrt/ccpp-2013-11-10-12:52:30-1946' exited with 1
                  12:52:30 localhost abrt-server[1948]: Deleting problem directory '/var/tmp/abrt/ccpp-2013-11-10-12:52:30-1946'


                  "...doesn't belong to any package..." leapt out at me.

                  Is there a way for me to set "ProcessUnpackaged" to 'yes'; and would that fix me up?




                • o11oo1oo
                  here s what showed up in that typescript file (gdb) run Starting program: /usr/local/bin/flamp [Thread debugging using libthread_db enabled] Using host
                  Message 8 of 15 , Nov 11, 2013
                  • 0 Attachment

                    here's what showed up in that typescript file


                    (gdb) run
                    Starting program: /usr/local/bin/flamp 
                    [Thread debugging using libthread_db enabled]
                    Using host libthread_db library "/lib/libthread_db.so.1".
                    terminate called after throwing an instance of 'SocketException'
                      what():  getaddrinfo: 127.0.0.1 : 7322: Address family for hostname not supported
                     
                    Program received signal SIGABRT, Aborted.
                    0xb7fff424 in __kernel_vsyscall ()
                    Missing separate debuginfos, use: debuginfo-install expat-2.1.0-4.fc18.i686 fltk-1.3.0-8.fc18.i686 fontconfig-2.10.2-2.fc18.i686 freetype-2.4.10-5.fc18.i686 glibc-2.16-34.fc18.i686 libX11-1.5.99.901-3.20130524gita3bdd2b09.fc18.i686 libXau-1.0.6-4.fc18.i686 libXcursor-1.1.13-5.20130524git8f677eaea.fc18.i686 libXext-1.3.1-3.20130524gitdfe6e1f3b.fc18.i686 libXfixes-5.0-6.20130524gitc480fe327.fc18.i686 libXft-2.3.1-2.fc18.i686 libXinerama-1.1.2-5.20130524git99c644fc8.fc18.i686 libXrender-0.9.7-5.20130524git786f78fd8.fc18.i686 libgcc-4.7.2-8.fc18.i686 libjpeg-turbo-1.2.90-1.fc18.i686 libpng-1.5.13-1.fc18.i686 libstdc++-4.7.2-8.fc18.i686 libxcb-1.9-3.fc18.i686 zlib-1.2.7-9.fc18.i686


                    i'm wondering if getting with fedora 19 might help. Don't suppose it could hurt.



                    ---In linuxham@yahoogroups.com, <o11oo1oo@...> wrote:

                    David, Jim, and all,


                    I'm still on Fedora 18 and it claims 32bits. The flamp ver is 2.1.01.


                    I was unaware of gdb. Will definitely give that a shot.


                    Thanks.


                    Dan



                    ---In linuxham@yahoogroups.com, <linuxham-fld@...> wrote:


                    By any chance are you running FLamp on a 64bit OS?  If so, this was a known issue on the last version of Flamp.  Make sure you're running the newest version. 

                    Beyond that, it looks like you're running a Fedora / RHEL / Centos box but the "post-create" on ... exited with 1" looks like a bug as there are lots of recent bug reports on that one.  You need to get the coredump to remain in /var/tmp/abrt/ccpp-* and once you can get there, running gdb against flamp and the core file should give us a backtrace to start troubleshooting things more.

                    --David
                    KI6ZHD



                     Do these messages I found in a log file mean anything to anybody here in regards to flamp failing to start unless i'm connected to the internet?


                    12:52:30 localhost abrt[1947]: Saved core dump of pid 1946 (/usr/local/bin/flamp) to /var/tmp/abrt/ccpp-2013-11-10-12:52:30-1946 (2011136 bytes)
                    12:52:30 localhost abrtd: New client connected
                    12:52:30 localhost abrt-server[1948]: Executable '/usr/local/bin/flamp' doesn't belong to any package and ProcessUnpackaged is set to 'no'
                    12:52:30 localhost abrt-server[1948]: 'post-create' on '/var/tmp/abrt/ccpp-2013-11-10-12:52:30-1946' exited with 1
                    12:52:30 localhost abrt-server[1948]: Deleting problem directory '/var/tmp/abrt/ccpp-2013-11-10-12:52:30-1946'


                    "...doesn't belong to any package..." leapt out at me.

                    Is there a way for me to set "ProcessUnpackaged" to 'yes'; and would that fix me up?




                  • David Ranch
                    Hello Dan, ... Hmmm.. what do you mean by typescript file? ... Strange that your computer is throwing an address family error and you re saying that when
                    Message 9 of 15 , Nov 11, 2013
                    • 0 Attachment

                      Hello Dan,

                      here's what showed up in that typescript file

                      Hmmm.. what do you mean by "typescript" file?


                      (gdb) run
                      Starting program: /usr/local/bin/flamp 
                      [Thread debugging using libthread_db enabled]
                      Using host libthread_db library "/lib/libthread_db.so.1".
                      terminate called after throwing an instance of 'SocketException'
                        what():  getaddrinfo: 127.0.0.1 : 7322: Address family for hostname not supported


                      Strange that your computer is throwing an "address family" error and you're saying that when connected to the Internet, you don't see this crash.  Hmmm... very strange.  The 127.0.0.1 network or "lo0" interface should be ALWAYS present on a running machine.  Were you able to get a copy of the core file to get a back trace from?  Before, the abrt directory was seemingly getting deleted for some reason.

                      Btw, where did you get this copy of Flamp?  Did you compile it?  Did you download it from a specific repo?



                      Program received signal SIGABRT, Aborted.
                      0xb7fff424 in __kernel_vsyscall ()
                      Missing separate debuginfos, use: debuginfo-install expat-2.1.0-4.fc18.i686 fltk-1.3.0-8.fc18.i686 fontconfig-2.10.2-2.fc18.i686 freetype-2.4.10-5.fc18.i686 glibc-2.16-34.fc18.i686 libX11-1.5.99.901-3.20130524gita3bdd2b09.fc18.i686 libXau-1.0.6-4.fc18.i686 libXcursor-1.1.13-5.20130524git8f677eaea.fc18.i686 libXext-1.3.1-3.20130524gitdfe6e1f3b.fc18.i686 libXfixes-5.0-6.20130524gitc480fe327.fc18.i686 libXft-2.3.1-2.fc18.i686 libXinerama-1.1.2-5.20130524git99c644fc8.fc18.i686 libXrender-0.9.7-5.20130524git786f78fd8.fc18.i686 libgcc-4.7.2-8.fc18.i686 libjpeg-turbo-1.2.90-1.fc18.i686 libpng-1.5.13-1.fc18.i686 libstdc++-4.7.2-8.fc18.i686 libxcb-1.9-3.fc18.i686 zlib-1.2.7-9.fc18.i686


                      You also might consider installing some of the these debug packages as instructed above which might help increase the debug output.

                      --David
                    • o11oo1oo
                      David, typescript is something that gdb gnu-debugger, suggested by w6jve,creates. I got flamp off the fldigi website, built from source per wiki
                      Message 10 of 15 , Nov 12, 2013
                      • 0 Attachment

                        David,


                        'typescript' is something that gdb gnu-debugger, suggested by w6jve,creates.


                        I got flamp off the fldigi website, built from source per wiki instructions.


                        i'll need to do a lot more reading about those other debuggers you pointed out. I didn't know what all that stuff was until you pointed it out.


                        And like I said, i think, i'm still on fedora18. Downloaded an Fc19 dvd last night, thinking it might solve something; but i havent pulled the update trigger as yet.


                        (wow is this new + improved ya hoo groups ever unecessarily confusing / slow!)



                        ---In linuxham@yahoogroups.com, <linuxham-fld@...> wrote:


                        Hello Dan,

                        here's what showed up in that typescript file

                        Hmmm.. what do you mean by "typescript" file?


                        (gdb) run
                        Starting program: /usr/local/bin/flamp 
                        [Thread debugging using libthread_db enabled]
                        Using host libthread_db library "/lib/libthread_db.so.1".
                        terminate called after throwing an instance of 'SocketException'
                          what():  getaddrinfo: 127.0.0.1 : 7322: Address family for hostname not supported


                        Strange that your computer is throwing an "address family" error and you're saying that when connected to the Internet, you don't see this crash.  Hmmm... very strange.  The 127.0.0.1 network or "lo0" interface should be ALWAYS present on a running machine.  Were you able to get a copy of the core file to get a back trace from?  Before, the abrt directory was seemingly getting deleted for some reason.

                        Btw, where did you get this copy of Flamp?  Did you compile it?  Did you download it from a specific repo?



                        Program received signal SIGABRT, Aborted.
                        0xb7fff424 in __kernel_vsyscall ()
                        Missing separate debuginfos, use: debuginfo-install expat-2.1.0-4.fc18.i686 fltk-1.3.0-8.fc18.i686 fontconfig-2.10.2-2.fc18.i686 freetype-2.4.10-5.fc18.i686 glibc-2.16-34.fc18.i686 libX11-1.5.99.901-3.20130524gita3bdd2b09.fc18.i686 libXau-1.0.6-4.fc18.i686 libXcursor-1.1.13-5.20130524git8f677eaea.fc18.i686 libXext-1.3.1-3.20130524gitdfe6e1f3b.fc18.i686 libXfixes-5.0-6.20130524gitc480fe327.fc18.i686 libXft-2.3.1-2.fc18.i686 libXinerama-1.1.2-5.20130524git99c644fc8.fc18.i686 libXrender-0.9.7-5.20130524git786f78fd8.fc18.i686 libgcc-4.7.2-8.fc18.i686 libjpeg-turbo-1.2.90-1.fc18.i686 libpng-1.5.13-1.fc18.i686 libstdc++-4.7.2-8.fc18.i686 libxcb-1.9-3.fc18.i686 zlib-1.2.7-9.fc18.i686


                        You also might consider installing some of the these debug packages as instructed above which might help increase the debug output.

                        --David
                      • Bob Snyder
                        ... Jut to set the record straight, files named typescript are created by script , a command line program that captures the terminal session into files that
                        Message 11 of 15 , Nov 12, 2013
                        • 0 Attachment
                          On 11/12/2013 04:01 PM, o11oo1oo@... wrote:

                          'typescript' is something that gdb gnu-debugger, suggested by w6jve,creates.



                          Jut to set the record straight, files named 'typescript' are created by 'script', a command line program that captures the terminal session into files that default to this name. Try 'man script' for details.

                          Bob W6CP

                        • o11oo1oo
                          RRR script, not gdb(1st time ive used either, so I m feeling like a moron) and, well, having little sucess on David s request for core dump . I think i follow
                          Message 12 of 15 , Nov 12, 2013
                          • 0 Attachment

                            RRR script, not gdb(1st time ive used either, so I'm feeling like a moron)


                            and, well, having little sucess on David's request for 'core dump'. I think i follow that my 'dump' is getting snagged by abrt. I went looking inn abrt and found this :



                            process /usr/local/bin/flam was killed by signal 6(SIGABRT)


                            --- Running report_uReport ---
                            Unable to open './pkg_epoch': No such file or directory.
                            reporter-ureport failed with exit code 1
                            ('report_uReport' exited with 1)


                            is this business about "./pkg_epoch" just letting me know that abrt isnt working without internet access or is it somehow related flamp crashing?


                            this is rapidly approaching (ok, possibly surpassing) the point of more work than it's worth.




                            ---In linuxham@yahoogroups.com, <bob.snyder@...> wrote:

                            On 11/12/2013 04:01 PM, o11oo1oo@... wrote:

                            'typescript' is something that gdb gnu-debugger, suggested by w6jve,creates.



                            Jut to set the record straight, files named 'typescript' are created by 'script', a command line program that captures the terminal session into files that default to this name. Try 'man script' for details.

                            Bob W6CP

                          • jhaynesatalumni
                            I think all this stuff about abrt and packages is just trying to tell you that the abrt system doesn t know where to send the bug report because the program
                            Message 13 of 15 , Nov 13, 2013
                            • 0 Attachment
                              I think all this stuff about abrt and packages is just trying to tell you that the abrt system
                              doesn't know where to send the bug report because the program didn't come from a package,
                              since you compiled it yourself.

                              Did you use the  bt  command from inside gdb to get a back trace?

                               




                            • o11oo1oo
                              Jim, i see what you mean now by backtrace. Here s what it gave me: (gdb) bt #0 0xb7fff424 in __kernel_vsyscall () #1 0x49904baf in raise () from
                              Message 14 of 15 , Nov 13, 2013
                              • 0 Attachment

                                 Jim,


                                i see what you mean now by backtrace. Here's what it gave me:


                                (gdb) bt
                                #0  0xb7fff424 in __kernel_vsyscall ()
                                #1  0x49904baf in raise () from /lib/libc.so.6
                                #2  0x49906503 in abort () from /lib/libc.so.6
                                #3  0x49f1f415 in __gnu_cxx::__verbose_terminate_handler() ()
                                   from /lib/libstdc++.so.6
                                #4  0x49f1cf64 in ?? () from /lib/libstdc++.so.6
                                #5  0x49f1cfa0 in std::terminate() () from /lib/libstdc++.so.6
                                #6  0x49f1d24f in __cxa_throw () from /lib/libstdc++.so.6
                                #7  0x08077ce0 in Address::lookup (this=this@entry=0x814c0b0, 
                                    proto_name=proto_name@entry=0x80ac74c "tcp") at ./utils/socket.cxx:315
                                #8  0x08077ddd in Address::Address (this=0x814c0b0, 
                                    host=0x80fab6c "127.0.0.1", port_name=0x80fab8c "7322", 
                                    proto_name=0x80ac74c "tcp") at ./utils/socket.cxx:228
                                #9  0x08050a55 in main (argc=1, argv=0xbffff234) at ./flamp.cxx:2740



                                ---In linuxham@yahoogroups.com, <jhhaynes@...> wrote:

                                I think all this stuff about abrt and packages is just trying to tell you that the abrt system
                                doesn't know where to send the bug report because the program didn't come from a package,
                                since you compiled it yourself.

                                Did you use the  bt  command from inside gdb to get a back trace?

                                 




                              • o11oo1oo
                                can t fathom as to why this error Address family for hostname not supported would have anything to do with having the wifi radio on this eeepc enabled , but
                                Message 15 of 15 , Dec 2, 2013
                                • 0 Attachment

                                  can't fathom as to why this error "Address family for hostname not supported" would have anything to do with having the wifi radio on this eeepc 'enabled', but last night I resolved my flamp-not-starting-and-throwing-SocketException issue when, in addition to just disconnecting the ethernet and wifi, I also 'disabled' the wifi.


                                  Now everything works fine with or without internet connectivity. Guess I just wasn't disconnected 'enough'. I wish I could say I'd figured this out by some method, but it was really just a pleasant surprise while flipping options on and off.



                                  ---In linuxham@yahoogroups.com, <o11oo1oo@...> wrote:

                                   Jim,


                                  i see what you mean now by backtrace. Here's what it gave me:


                                  (gdb) bt
                                  #0  0xb7fff424 in __kernel_vsyscall ()
                                  #1  0x49904baf in raise () from /lib/libc.so.6
                                  #2  0x49906503 in abort () from /lib/libc.so.6
                                  #3  0x49f1f415 in __gnu_cxx::__verbose_terminate_handler() ()
                                     from /lib/libstdc++.so.6
                                  #4  0x49f1cf64 in ?? () from /lib/libstdc++.so.6
                                  #5  0x49f1cfa0 in std::terminate() () from /lib/libstdc++.so.6
                                  #6  0x49f1d24f in __cxa_throw () from /lib/libstdc++.so.6
                                  #7  0x08077ce0 in Address::lookup (this=this@entry=0x814c0b0, 
                                      proto_name=proto_name@entry=0x80ac74c "tcp") at ./utils/socket.cxx:315
                                  #8  0x08077ddd in Address::Address (this=0x814c0b0, 
                                      host=0x80fab6c "127.0.0.1", port_name=0x80fab8c "7322", 
                                      proto_name=0x80ac74c "tcp") at ./utils/socket.cxx:228
                                  #9  0x08050a55 in main (argc=1, argv=0xbffff234) at ./flamp.cxx:2740



                                  ---In linuxham@yahoogroups.com, <jhhaynes@...> wrote:

                                  I think all this stuff about abrt and packages is just trying to tell you that the abrt system
                                  doesn't know where to send the bug report because the program didn't come from a package,
                                  since you compiled it yourself.

                                  Did you use the  bt  command from inside gdb to get a back trace?

                                   




                                Your message has been successfully submitted and would be delivered to recipients shortly.