Menu ▾ ▴

#95 Mac OS X security update 2005-007 break wrapper.

v3.1.2
open
nobody
5
2012-12-11
2005-08-17
Anonymous
No

After the latest Security Update 2005-007 1.0 was automatically
installed on OS X 10.4.2, the wrapper stopped working and now
throughs a dyld bind error for the symbol "_ftime".

The library in question is still there, but it was replaced when the
security update was installed with a new version that apparently
doesn't have this interface?

This is pretty serious because it means that anyone using the
wrapper will be zapped the moment this security update patch in
installed, and since it is a security update and not an OS upgrade I
would guess that most people will automatically install it (which is a
one-way trip).

wrapper | --> Wrapper Started as Console
dyld: lazy symbol binding failed: Symbol not found: _ftime
Referenced from: /Users/bryan/Projects/PT/Hydrogen/main/target/
plumtree/common/container/jboss/3.2.7/bin/../../../../wrapper/3.1.2/
bin/native/macosx/wrapper
Expected in: /usr/lib/libcrypto.0.9.7.dylib

dyld: Symbol not found: _ftime
Referenced from: /Users/bryan/Projects/PT/Hydrogen/main/target/
plumtree/common/container/jboss/3.2.7/bin/../../../../wrapper/3.1.2/
bin/native/macosx/wrapper
Expected in: /usr/lib/libcrypto.0.9.7.dylib

Trace/BPT trap

Discussion

  • Andreas

    Andreas - 2005-08-18

    Logged In: YES
    user_id=510665

    Hello,

    just wanted to add the note I experienced the same problem on Mac OS X
    10.3.9 after the security update has been installed.

    In the Apple documentation it says the ftime function is obsolete ( => http:
    //developer.apple.com/documentation/Darwin/Reference/ManPages/man3/
    ftime.3.html ) so I don't think they will fix that problem...

     
  • Andreas

    Andreas - 2005-08-18

    Logged In: YES
    user_id=510665

    I created a little patch to fix this. Have a look at http://sourceforge.net/
    tracker/index.php?
    func=detail&aid=1263265&group_id=39428&atid=425189

     
  • Alphonse Bendt

    Alphonse Bendt - 2005-08-25

    Logged In: YES
    user_id=1092966

    i had the same problem. so i tried recompiling the wrapper (v 3.1.2). i also
    had to apply a patch to compile the wrapper although my changes are
    more simple.

    patch is available here: http://sourceforge.net/tracker/index.php?
    func=detail&aid=1273349&group_id=39428&atid=425189

     

Log in to post a comment.