Menu ▾ ▴

#76 6.1.4 crashed with sigsegv, how can I diagnose?

v6.1.4
open-accepted
iODBC Maintainer
None
5
2012-02-02
2012-01-22
Benson Margulies
No

Here's the tail of the log:

15:15:28 Checkpoint finished, log reused
15:24:56 GPF: sched_pthread.c:933 semaphore_enter() failed
15:24:56 Server received signal 11. Continuing with the default action for that signal.

I suspect that I can repro this at will. At the time of the failure, a client was shoving RDF into the database via the Jena connector and thus jdbc3.

Discussion

  • Benson Margulies

    Benson Margulies - 2012-01-22

    It might be relevant that I'm on Lion.

     

  • iODBC Maintainer

    iODBC Maintainer - 2012-02-02
    • assigned_to: nobody --> iodbc
    • status: open --> open-accepted
     

  • iODBC Maintainer

    iODBC Maintainer - 2012-02-02

    Can you report your OS and version please?

     

  • Benson Margulies

    Benson Margulies - 2012-02-03

    Mac OSX 10.7.2 (Lion)

     

  • iODBC Maintainer

    iODBC Maintainer - 2012-02-03

    Proposed patch for issue with threads on Mac OS X 10.7

     
    vos-6.1.4-threads-macosx-10.7.diff

  • iODBC Maintainer

    iODBC Maintainer - 2012-02-03

    I have added a proposed patch for Mac OS X 10.7 to this bugreport, which we think will resolve the problem.

    Please test it on your installation and let me know if it works for you.

     

  • Till Adam

    Till Adam - 2012-02-18

    I was seeing a very similar crash using virtuoso through KDE's nepomuk library on OSX Lion. I can confirm that the patch attached to this issues seems to fix the problem.

     

Log in to post a comment.

MongoDB Logo MongoDB