On Mon, 15 Nov 2004 18:12:51 -0500 Bart Elberg <[EMAIL PROTECTED]> babbled:
(B
(B> Looks like we have a similar problem and IT IS CRITICAL FOR US TO SOLVE
(B> THIS!!
(B>
(B> We're integrating our existing application libraries with an EFL-based
(B> GUI and once we start linking with libedb it core dumps. The trace looks
(B> like this:
(B
(Bsomething else is pulling in a libdb (-ldb) link (another shared lib or an
(Bexplicit link). since edb is originally a fork of libdb2 (sleepycat's libdb2.7)
(Bwith just a nice wrapper on top (due to libdb changing on-disk format every
(Bminor version or 2 and thus making it impossible to open files created when
(Blinked to a previous libdb) - it shares internal symbol names and this does
(Bscrew things up. the solution is more or less a lot of mind-numbingly boring
(B"sed" work with symbols in the code (also being careful to not be too zealous
(Band change something that is a substring of something else).
(B
(B> > #0 0x40150457 in __edb_os_abspath () from /usr/lib/libedb.so.1
(B> > (gdb) where
(B> > #0 0x40150457 in __edb_os_abspath () from /usr/lib/libedb.so.1
(B> > #1 0x4015e314 in __log_name () from /usr/lib/libedb.so.1
(B> > #2 0x00000002 in ?? ()
(B> > #3 0x2f656369 in ?? ()
(B> > #4 0x4282cfa0 in ?? ()
(B> > #5 0x00000000 in ?? ()
(B> > #6 0x00000000 in ?? ()
(B> > #7 0x4282d048 in ?? ()
(B> > #8 0x05d39a74 in ?? ()
(B> > #9 0x40c10188 in ?? () from /office/development/FAPFS/lib/libdb_cxx-4.2.so
(B> > #10 0x40129664 in ?? () from /usr/lib/libedb.so.1
(B> > #11 0x401084e8 in ?? ()
(B> > #12 0x41016c40 in ?? () from /lib/ld-linux.so.2
(B> > #13 0x2e676f6c in ?? ()
(B> > #14 0x30303030 in ?? ()
(B> > #15 0x30303030 in ?? ()
(B> > #16 0x41003130 in ?? () from /lib/ld-linux.so.2
(B> > #17 0x40108684 in ?? ()
(B> > #18 0x00000001 in ?? ()
(B> > #19 0x00000001 in ?? ()
(B> > #20 0x40cb97f9 in __os_free () from
(B> > /office/development/FAPFS/lib/libdb_cxx-4.2.so Previous frame inner to this
(B> > frame (corrupt stack?)(gdb) quit
(B>
(B> Suspecting a symbol conflict, we tried changing "__log_name" to
(B> "__edb_log_name" and rebuilding e17. Got the same error with the new
(B> symbol name.
(B>
(B> Has anyone found a workaround to this problem?
(B>
(B> Thanks!
(B>
(B> --
(B> Bart Elberg
(B>
(B> I.D.E.A.L. Technology Corporation
(B> http://www.idealcorp.com
(B>
(B>
(B>
(B>
(B>
(B> -------------------------------------------------------
(B> This SF.Net email is sponsored by: InterSystems CACHE
(B> FREE OODBMS DOWNLOAD - A multidimensional database that combines
(B> robust object and relational technologies, making it a perfect match
(B> for Java, C++,COM, XML, ODBC and JDBC. www.intersystems.com/match8
(B> _______________________________________________
(B> enlightenment-devel mailing list
(B> [EMAIL PROTECTED]
(B> https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
(B>
(B
(B
(B--
(B------------- Codito, ergo sum - "I code, therefore I am" --------------
(BThe Rasterman (Carsten Haitzler) [EMAIL PROTECTED]
$BMg9%B?(B [EMAIL PROTECTED]
(BTokyo, Japan ($BEl5~(B $BF|K\(B)
(B
(B
(B-------------------------------------------------------
(BThis SF.Net email is sponsored by: InterSystems CACHE
(BFREE OODBMS DOWNLOAD - A multidimensional database that combines
(Brobust object and relational technologies, making it a perfect match
(Bfor Java, C++,COM, XML, ODBC and JDBC. www.intersystems.com/match8
(B_______________________________________________
(Benlightenment-devel mailing list
([EMAIL PROTECTED]
(Bhttps://lists.sourceforge.net/lists/listinfo/enlightenment-devel
