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

Re: [linuxham] Re: fldigi-3.21.72 and OS X 10.8.4 crashing

Expand Messages
  • Robert Stiles
    Greg,  After looking at the code, the error is likely with your fonts. I can add code to check for the divide by zero which will fix the crashing issue.
    Message 1 of 12 , Jun 25, 2013
    • 0 Attachment
      Greg, 

      After looking at the code, the error is likely with your fonts.

      I can add code to check for the divide by zero which will fix the crashing issue. However, I suspect the font being used will not display correctly.

      Robert



      From: Greg Drew <gdrew@...>
      To: linuxham@yahoogroups.com
      Sent: Monday, June 24, 2013 6:50 PM
      Subject: Re: [linuxham] Re: fldigi-3.21.72 and OS X 10.8.4 crashing

       
      Older versions have run successfully, but that was several Apple OS updates ago.  It has been a while since I ran fldigi, and when I tried the old previously working version yesterday it failed, so I downloaded the latest assuming that some update from Apple had pushed an incompatible library, but obviously that was not the issue.
      --GDD/N3MXX

      On 6/24/13 7:46 PM, Tom_Pryts wrote:
       
      I have got to agree with Scott on the best way to try to get Fldigi running.
      One question. Did it ever run ok or has it done this from the start?

      --- In linuxham@yahoogroups.com, "Cliff Scott" <ae5za@...> wrote:
      >
      > ** Reply to message from "Greg" <gdrew@...> on Mon, 24 Jun 2013
      > 22:58:47 -0000
      >
      > Hmmm. Strange. I'm running Fldigi on MacbookPro OSx 10.7.5 without problems.
      > Your error report mentions a "divide by zero error". That often means
      > something has gotten out of bounds. It's a wild shot, but you might try
      > redownloading Fldigi, deleting all of the old stuff as you have already done
      > once and install the new download. Just, maybe there was an error in the
      > downloading that wasn't caught on the install process. Something has to be
      > not right either in the download or "gasp" in your system as many of us are
      > using it on the Mac without problems.
      >
      > > I'm having problems with fldigi crashing on startup on OS X. I get the
      > > "fldigi has quite unexpectedly' message. I've tried the usual things -
      > > deleting and reinstalling, as well as removing .fldigi. I've also tried
      > > running "fix permissions" as suggested by another post, and have gone down to
      > > the command line and manually removed everything related to fldigi. Nothing
      > > has worked. Has anyone run into a similar problem? Examining posts here, it
      > > looks like other people have it working.
      > >
      > > The system is a MacBook Pro, 8GB, OSX 10.8.4, 2.5Ghz Core i7.
      > >
      > > Here is the [partial] crash report:
      > >
      > > Process: fldigi [1400]
      > > Path: /Applications/fldigi-3.21.72.app/Contents/MacOS/fldigi
      > > Identifier: com.w1hkj.fldigi
      > > Version: 3.21 (3.21)
      > > Code Type: X86 (Native)
      > > Parent Process: launchd [278]
      > > User ID: 501
      > >
      > > Date/Time: 2013-06-24 18:57:46.624 -0400
      > > OS Version: Mac OS X 10.8.4 (12E55)
      > > Report Version: 10
      > >
      > > Interval Since Last Report: 2995 sec
      > > Crashes Since Last Report: 5
      > > Per-App Interval Since Last Report: 1 sec
      > > Per-App Crashes Since Last Report: 5
      > > Anonymous UUID: 7152C645-5CA7-2C03-84BE-152F65D69E86
      > >
      > > Crashed Thread: 0 Dispatch queue: com.apple.main-thread
      > >
      > > Exception Type: EXC_ARITHMETIC (SIGFPE)
      > > Exception Codes: EXC_I386_DIV (divide by zero)
      > >
      > > Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
      > > 0 com.w1hkj.fldigi 0x002154f9 pskBrowser::pskBrowser(int, int, int, int, char const*) + 559
      > > 1 com.w1hkj.fldigi 0x000e1343 create_fl_digi_main_primary() + 16633
      > > 2 com.w1hkj.fldigi 0x000e42cf create_fl_digi_main(int, char**) + 147
      > > 3 com.w1hkj.fldigi 0x00133f77 main + 4577
      > > 4 com.w1hkj.fldigi 0x00002746 _start + 216
      > > 5 com.w1hkj.fldigi 0x0000266d start + 41
      > >
      > > Thread 1:: Dispatch queue: com.apple.libdispatch-manager
      > > 0 libsystem_kernel.dylib 0x95cb89ae kevent + 10
      > > 1 libdispatch.dylib 0x96e8ac71 _dispatch_mgr_invoke + 993
      > > 2 libdispatch.dylib 0x96e8a7a9 _dispatch_mgr_thread + 53
      > >
      > > Thread 2:
      > > 0 libsystem_kernel.dylib 0x95cb80ee __workq_kernreturn + 10
      > > 1 libsystem_c.dylib 0x918910ac _pthread_workq_return + 45
      > > 2 libsystem_c.dylib 0x91890e79 _pthread_wqthread + 448
      > > 3 libsystem_c.dylib 0x91878d2a start_wqthread + 30
      > >
      > > Thread 3:
      > > 0 libsystem_kernel.dylib 0x95cb80ee __workq_kernreturn + 10
      > > 1 libsystem_c.dylib 0x918910ac _pthread_workq_return + 45
      > > 2 libsystem_c.dylib 0x91890e79 _pthread_wqthread + 448
      > > 3 libsystem_c.dylib 0x91878d2a start_wqthread + 30
      > >
      > > Thread 4:
      > > 0 libsystem_kernel.dylib 0x95cb80ee __workq_kernreturn + 10
      > > 1 libsystem_c.dylib 0x918910ac _pthread_workq_return + 45
      > > 2 libsystem_c.dylib 0x91890e79 _pthread_wqthread + 448
      > > 3 libsystem_c.dylib 0x91878d2a start_wqthread + 30
      > >
      > > Thread 0 crashed with X86 Thread State (32-bit):
      > > eax: 0x00000126 ebx: 0x002152d8 ecx: 0x00003f01 edx: 0x00000000
      > > edi: 0x0000001e esi: 0x00a5ed60 ebp: 0xbffff058 esp: 0xbfffeff0
      > > ss: 0x00000023 efl: 0x00010202 eip: 0x002154f9 cs: 0x0000001b
      > > ds: 0x00000023 es: 0x00000023 fs: 0x00000000 gs: 0x0000000f
      > > cr2: 0x0029a330
      > > Logical CPU: 0
      >




    • Greg Drew
      Thanks to everyone on the group for their suggestions, and especially to Robert Stiles who dug into the code, made a fix, and sent me a dev version to test
      Message 2 of 12 , Jun 26, 2013
      • 0 Attachment
        Thanks to everyone on the group for their suggestions, and especially to Robert Stiles who dug into the code, made a fix, and sent me a dev version to test which resolved the issue.

        In case anyone else has the same problem, it was caused by a bad font in the system.  The next version of fldigi will contain the fix, which will avoid the problem entirely.  Of course, the bad font that caused the issue would still be there.  If one wants to get rid of bad fonts, you can try the following.

        I was able to get the old version to work after using the "Font Book" utility to identify the bad fonts (select them all and chose Validate Fonts from the File menu).  I manually removed the bad one from the /Library/Fonts folder, I also used the same utility to restore the system fonts.

        --GDD/N3MXX

        On 6/25/13 1:21 PM, Robert Stiles wrote:
         
        Greg, 

        After looking at the code, the error is likely with your fonts.

        I can add code to check for the divide by zero which will fix the crashing issue. However, I suspect the font being used will not display correctly.

        Robert



        From: Greg Drew <gdrew@...>
        To: linuxham@yahoogroups.com
        Sent: Monday, June 24, 2013 6:50 PM
        Subject: Re: [linuxham] Re: fldigi-3.21.72 and OS X 10.8.4 crashing

         
        Older versions have run successfully, but that was several Apple OS updates ago.  It has been a while since I ran fldigi, and when I tried the old previously working version yesterday it failed, so I downloaded the latest assuming that some update from Apple had pushed an incompatible library, but obviously that was not the issue.
        --GDD/N3MXX

        On 6/24/13 7:46 PM, Tom_Pryts wrote:
         
        I have got to agree with Scott on the best way to try to get Fldigi running.
        One question. Did it ever run ok or has it done this from the start?

        --- In linuxham@yahoogroups.com, "Cliff Scott" <ae5za@...> wrote:
        >
        > ** Reply to message from "Greg" <gdrew@...> on Mon, 24 Jun 2013
        > 22:58:47 -0000
        >
        > Hmmm. Strange. I'm running Fldigi on MacbookPro OSx 10.7.5 without problems.
        > Your error report mentions a "divide by zero error". That often means
        > something has gotten out of bounds. It's a wild shot, but you might try
        > redownloading Fldigi, deleting all of the old stuff as you have already done
        > once and install the new download. Just, maybe there was an error in the
        > downloading that wasn't caught on the install process. Something has to be
        > not right either in the download or "gasp" in your system as many of us are
        > using it on the Mac without problems.
        >
        > > I'm having problems with fldigi crashing on startup on OS X. I get the
        > > "fldigi has quite unexpectedly' message. I've tried the usual things -
        > > deleting and reinstalling, as well as removing .fldigi. I've also tried
        > > running "fix permissions" as suggested by another post, and have gone down to
        > > the command line and manually removed everything related to fldigi. Nothing
        > > has worked. Has anyone run into a similar problem? Examining posts here, it
        > > looks like other people have it working.
        > >
        > > The system is a MacBook Pro, 8GB, OSX 10.8.4, 2.5Ghz Core i7.
        > >
        > > Here is the [partial] crash report:
        > >
        > > Process: fldigi [1400]
        > > Path: /Applications/fldigi-3.21.72.app/Contents/MacOS/fldigi
        > > Identifier: com.w1hkj.fldigi
        > > Version: 3.21 (3.21)
        > > Code Type: X86 (Native)
        > > Parent Process: launchd [278]
        > > User ID: 501
        > >
        > > Date/Time: 2013-06-24 18:57:46.624 -0400
        > > OS Version: Mac OS X 10.8.4 (12E55)
        > > Report Version: 10
        > >
        > > Interval Since Last Report: 2995 sec
        > > Crashes Since Last Report: 5
        > > Per-App Interval Since Last Report: 1 sec
        > > Per-App Crashes Since Last Report: 5
        > > Anonymous UUID: 7152C645-5CA7-2C03-84BE-152F65D69E86
        > >
        > > Crashed Thread: 0 Dispatch queue: com.apple.main-thread
        > >
        > > Exception Type: EXC_ARITHMETIC (SIGFPE)
        > > Exception Codes: EXC_I386_DIV (divide by zero)
        > >
        > > Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
        > > 0 com.w1hkj.fldigi 0x002154f9 pskBrowser::pskBrowser(int, int, int, int, char const*) + 559
        > > 1 com.w1hkj.fldigi 0x000e1343 create_fl_digi_main_primary() + 16633
        > > 2 com.w1hkj.fldigi 0x000e42cf create_fl_digi_main(int, char**) + 147
        > > 3 com.w1hkj.fldigi 0x00133f77 main + 4577
        > > 4 com.w1hkj.fldigi 0x00002746 _start + 216
        > > 5 com.w1hkj.fldigi 0x0000266d start + 41
        > >
        > > Thread 1:: Dispatch queue: com.apple.libdispatch-manager
        > > 0 libsystem_kernel.dylib 0x95cb89ae kevent + 10
        > > 1 libdispatch.dylib 0x96e8ac71 _dispatch_mgr_invoke + 993
        > > 2 libdispatch.dylib 0x96e8a7a9 _dispatch_mgr_thread + 53
        > >
        > > Thread 2:
        > > 0 libsystem_kernel.dylib 0x95cb80ee __workq_kernreturn + 10
        > > 1 libsystem_c.dylib 0x918910ac _pthread_workq_return + 45
        > > 2 libsystem_c.dylib 0x91890e79 _pthread_wqthread + 448
        > > 3 libsystem_c.dylib 0x91878d2a start_wqthread + 30
        > >
        > > Thread 3:
        > > 0 libsystem_kernel.dylib 0x95cb80ee __workq_kernreturn + 10
        > > 1 libsystem_c.dylib 0x918910ac _pthread_workq_return + 45
        > > 2 libsystem_c.dylib 0x91890e79 _pthread_wqthread + 448
        > > 3 libsystem_c.dylib 0x91878d2a start_wqthread + 30
        > >
        > > Thread 4:
        > > 0 libsystem_kernel.dylib 0x95cb80ee __workq_kernreturn + 10
        > > 1 libsystem_c.dylib 0x918910ac _pthread_workq_return + 45
        > > 2 libsystem_c.dylib 0x91890e79 _pthread_wqthread + 448
        > > 3 libsystem_c.dylib 0x91878d2a start_wqthread + 30
        > >
        > > Thread 0 crashed with X86 Thread State (32-bit):
        > > eax: 0x00000126 ebx: 0x002152d8 ecx: 0x00003f01 edx: 0x00000000
        > > edi: 0x0000001e esi: 0x00a5ed60 ebp: 0xbffff058 esp: 0xbfffeff0
        > > ss: 0x00000023 efl: 0x00010202 eip: 0x002154f9 cs: 0x0000001b
        > > ds: 0x00000023 es: 0x00000023 fs: 0x00000000 gs: 0x0000000f
        > > cr2: 0x0029a330
        > > Logical CPU: 0
        >





      • h3n5y
        Greg, Robert s remark about fonts reminded me of a recent MacBreakWeekly podcasts where they mentioned similar issues (with other software) which was fixed by
        Message 3 of 12 , Jun 26, 2013
        • 0 Attachment
          Greg,

          Robert's remark about fonts reminded me of a recent MacBreakWeekly podcasts where they mentioned similar issues (with other software) which was fixed by clearing the font cache on your Mac.

          You might want to give that a try, simple and easy.

          How to do that? Look here:
          http://www.extensis.com/support/knowledge-base/clearing-the-mac-os-x-font-cache/

          73 de heinz, VK2STM

          --- In linuxham@yahoogroups.com, Robert Stiles <kk5vd@...> wrote:
          >
          > Greg, 
          >
          > After looking at the code, the error is likely with your fonts.
          >
          > I can add code to check for the divide by zero which will fix the crashing issue. However, I suspect the font being used will not display correctly.
          >
          > Robert
          >
          >
        Your message has been successfully submitted and would be delivered to recipients shortly.