[Dpcl-user] Re: ASC_invalid_pid for DPCL 3.2.1 C
Brought to you by:
dpcl-admin,
dwootton
From: <joh...@us...> - 2001-04-04 21:03:44
|
Hi, The PoeAppl::bcreate call is implemented by calling other dpcl calls. PoeAppl::bcreate basically does the following: * set up envp for poe - add _MP_DBG_STOP_TASK=1 * start poe * install probe at pe_dbg_breakpoint * when probe hit for the second time, attach config file done, remove probe * read attach config file * connect to poe app - with ptrace PT_REATT Perhaps one of these is failing with an ASC_invalid_pid. To gather client side debug output, compile libdpcl.a with DEBUG_CLIENT defined or send a test case and we'll try that. To gather daemon side debug output, use the Ais_blog_on call just before the call to bcreate. For example: AisStatus lsts = Ais_blog_on(host, LGL_detail, LGD_daemon, NULL, NULL); Log files will be generated with names like /tmp/dpclsd."daemon_pid". As Ted has mentioned, these may be very large files. Keeping the number of procs small helps keep these log files smaller. Regarding software levels. On our 4.3.3 system we have successfully used bos.mp 4.3.3.26 and 4.3.3.30, and bos.rte.libpthreads 4.3.3.26 and 4.3.3.29. Regards, John |