Re: Hi Please help on back-sql...

["Dmitry Kovalev" <mitya@seismic.geol.msu.ru>]

The reason also could be:
1) in more general threading problems on Solaris (check the FAQs - maybe
there is smth. about it)
2) in tha, according to the log, you did not populate the metadata table, so
there are no mappings loaded - maybe this is the problem - it is unclear
from the log, where exactly the bad thing strikes, so in any case - you
should find this out more precisely

----- Original Message -----
From: "Dmitry Kovalev" <mitya@seismic.geol.msu.ru>
To: "sajida kalsoom" <sajida@advcomm.net>; <openldap-software@OpenLDAP.org>
Sent: Monday, July 30, 2001 4:18 PM
Subject: Re: Hi Please help on back-sql...


> > ==>backsql_close_db_conn()
> > signal fault in critical section
> > signal number: 11, signal code: 1,                          fault
address:
> > 0x478, pc: 0xef7d9c60, sp: 0xefffec20
> > libthread panic: fault in libthread critical section (PID: 1204 LWP 1)
> > stacktrace:
> >         ef7d9c2c
> > ...
> > ###################################
> > what could b reason.. if any one can help me in this regard.
> > Thanks in advanced.
>
> Most probably, the database access package you use is not thread-safe...
You
> could assure it if you localize the place it happens by adding more debug
> output to backsql_close_db_conn(). If it happens in an ODBC call - then
the
> problem is there.
>
> WBW, Dmitry
>
>