Kevin R. Bulgrien wrote: The above is a normal occurence if a client is shut down. SIGPIPE signals han be ignored. Can't remember the precise syntax in GDB to do that - something like 'handle SIGPIPE nostop', but not sure on that. > > Program received signal SIGPIPE, Broken pipe. > 0x4016a384 in write () from /lib/libc.so.6 > (gdb) where > #0 0x4016a384 in write () from /lib/libc.so.6 > #1 0xbfffc8f0 in ?? () > #2 0x080c1b92 in Send_With_Handling (ns=0x9159714, msg=0xbfffc8f0) > at lowlevel.c:414 > #3 0x080c43a0 in esrv_map_doneredraw (ns=0x9159714, newmap=0xbfffc950) > at request.c:888 > #4 0x080c5ea4 in draw_client_map (pl=0x8121ed0) at request.c:1456 > #5 0x080c14d6 in doeric_server () at loop.c:631 > #6 0x08068ebf in main (argc=1, argv=0xbffff954) at main.c:1156 > #7 0x400a4280 in __libc_start_main () from /lib/libc.so.6 > (gdb) > _______________________________________________ > crossfire-devel mailing list > crossfire-devel at lists.real-time.com > https://mailman.real-time.com/mailman/listinfo/crossfire-devel