You can find the core file at

http://www.lsc-group.phys.uwm.edu/lscdatagrid/downloads/ldr_software/globus-rls-server.core

I've been trying to get a look at the core file. Was this binary on a sparc
architecture or x86? I used gdb and mdb on a sparc sol9 box to look at the core
file but I didn't get much info out of it.

In the meantime... If someone could open the core file with gdb and give me the
output of 'backtrace' that would help.

Also, if I remember correctly you build your binaries withOUT debug symbols.

It was/is a Solaris 10 box:

[grid@ldas-cit skoranda]$ uname -a
SunOS ldas-cit 5.10 Generic_127111-11 sun4u sparc SUNW,Sun-Fire-880

The backtrace from the core file is 

(gdb) backtrace
#0  0xfe945b84 in _lwp_kill () from /lib/libc.so.1
#1  0xfe8e4bbc in raise () from /lib/libc.so.1
#2  0xfe8c10c0 in abort () from /lib/libc.so.1
#3  0xfef33078 in globus_silent_fatal () at globus_print.c:57
#4  0xfef33124 in globus_fatal (
    msg=0xfef4a248 "%s %s\n%s unknown error number: %d\n") at globus_print.c:88
#5  0xfef39644 in globus_i_thread_report_bad_rc (rc=59,
    message=0xfef4a620 "GLOBUSTHREAD: pthread_mutex_lock() failed\n")
    at globus_thread_common.c:138
#6  0xfef3b21c in globus_mutex_lock (mut=0x27455b70)
    at globus_thread_pthreads.c:823
#7  0xff294928 in globus_io_register_writev (handle=0x2599c7b0,
    iov=0xfc5fb220, iovcnt=2, writev_callback=0xff2feaa8 <writevcb>,
    callback_arg=0xfc5fb160) at globus_io_xio_compat.c:3236
#8  0xff2fe36c in rrpc_writev (h=0x2599c7b0, iov=0xfc5fb220, iovcnt=2,
    nbw=0xfc5fb230, errmsg=0x259a07d4 "L-R-894811392-32.gwf,0") at rpc.c:317
#9  0x0002ba7c in rrpc_error (c=0x2599c7b0, rc=12, fmt=0x3b6d0 "%s")
    at server.c:1376
#10 0x0002e14c in lrc_exists (c=0x2599c7b0, dbh=0xfc5fbf4c, arglist=0xfc5fbf58)
    at server.c:1950
#11 0x0002a65c in procreq (a=0x0) at server.c:1054
#12 0xfe944998 in _lwp_start () from /lib/libc.so.1
#13 0xfe944998 in _lwp_start () from /lib/libc.so.1
---Type <return> to continue, or q <return> to quit---
Backtrace stopped: previous frame identical to this frame (corrupt stack?)

We build our LDR binaries with debug symbols (gcc32dbgpthr).

Most of the below RLS functions are in replica/rls/server/server.c the last one
is in replica/rls/client/library/rpc.c -- not that I expect you'll be looking
into them but just in case. The lifecycle of the connection follows the path:

globus_io_tcp_register_listen
 || 
 \/
lisetncb: checks for io error condition
 ||
 \/
doaccept: sets security attributes on io handle
 ||
 \/
globus_io_tcp_register_accept
 ||
 \/
acceptcb: checks some RLS error conditions
 ||
 \/
globus_io_register_read
 ||
 \/
readcb: queue's the handle (inside an RLS connection object)
 ||
 \/
-- at this point the connection is placed on a "request queue" internal to the
RLS. Then a request processing thread is notified (waiting on a condition var)
that a request is ready for processing.
 ||
 \/
procereq(): wakes and inspects the request and calls a function (in the case of
the crash the function called was lrc_exists()
 ||
 \/
lrc_exists(): makes a db call (in this case the application logic is to report
an "error" that the object the caller was looking for didn't exist in the RLS
database -- but not a system error to be clear)
 ||
 \/
rrpc_error(): creates its iovec structure with the error message
 ||
 \/
rrpc_writev() -- found in rpc.c: initializes a mutex/cv to be used by the
writevcb (never reached)
 ||
 \/
globus_io_register_writev
 ||
 \/
*BANG*

It seems a pretty simple case of listen->accept->read->write->close.

You can find two log files for the RLS server running on this platform/machine
at

http://www.lsc-group.phys.uwm.edu/lscdatagrid/downloads/ldr_software/rls.log.1.gz
http://www.lsc-group.phys.uwm.edu/lscdatagrid/downloads/ldr_software/rls.log.2.gz