| Server IP : 103.119.228.120 / Your IP : 3.140.186.189 Web Server : Apache System : Linux v8.techscape8.com 3.10.0-1160.119.1.el7.tuxcare.els2.x86_64 #1 SMP Mon Jul 15 12:09:18 UTC 2024 x86_64 User : nobody ( 99) PHP Version : 5.6.40 Disable Function : shell_exec,symlink,system,exec,proc_get_status,proc_nice,proc_terminate,define_syslog_variables,syslog,openlog,closelog,escapeshellcmd,passthru,ocinum cols,ini_alter,leak,listen,chgrp,apache_note,apache_setenv,debugger_on,debugger_off,ftp_exec,dl,dll,myshellexec,proc_open,socket_bind,proc_close,escapeshellarg,parse_ini_filepopen,fpassthru,exec,passthru,escapeshellarg,escapeshellcmd,proc_close,proc_open,ini_alter,popen,show_source,proc_nice,proc_terminate,proc_get_status,proc_close,pfsockopen,leak,apache_child_terminate,posix_kill,posix_mkfifo,posix_setpgid,posix_setsid,posix_setuid,dl,symlink,shell_exec,system,dl,passthru,escapeshellarg,escapeshellcmd,myshellexec,c99_buff_prepare,c99_sess_put,fpassthru,getdisfunc,fx29exec,fx29exec2,is_windows,disp_freespace,fx29sh_getupdate,fx29_buff_prepare,fx29_sess_put,fx29shexit,fx29fsearch,fx29ftpbrutecheck,fx29sh_tools,fx29sh_about,milw0rm,imagez,sh_name,myshellexec,checkproxyhost,dosyayicek,c99_buff_prepare,c99_sess_put,c99getsource,c99sh_getupdate,c99fsearch,c99shexit,view_perms,posix_getpwuid,posix_getgrgid,posix_kill,parse_perms,parsesort,view_perms_color,set_encoder_input,ls_setcheckboxall,ls_reverse_all,rsg_read,rsg_glob,selfURL,dispsecinfo,unix2DosTime,addFile,system,get_users,view_size,DirFiles,DirFilesWide,DirPrintHTMLHeaders,GetFilesTotal,GetTitles,GetTimeTotal,GetMatchesCount,GetFileMatchesCount,GetResultFiles,fs_copy_dir,fs_copy_obj,fs_move_dir,fs_move_obj,fs_rmdir,SearchText,getmicrotime MySQL : ON | cURL : ON | WGET : ON | Perl : ON | Python : ON | Sudo : ON | Pkexec : ON Directory : /usr/local/ssl/local/ssl/local/ssl/share/doc/pth-2.0.7/ |
Upload File : |
____ _ _ | _ \| |_| |__ ``Programming is like sex - | |_) | __| '_ \ one mistake and you have | __/| |_| | | | to support it for the rest |_| \__|_| |_| of your life.'' GNU Pth - The GNU Portable Threads SUPPORT ======= If you want to discuss multithreading issues not directly related to GNU Pth, post to the USENET newsgroup comp.programming.threads. There you can reach mostly all authorities of multithreading. In case you have problems directly related to GNU Pth or you need technical support for programming with GNU Pth, you can send a bug report to bug-pth@gnu.org or alternatively write to the GNU Pth support mailing list pth-users@gnu.org. There you can currently (as of August 2000) reach about 110 Pth users from around the world. Old pth-users@gnu.org postings are archived at http://www.mail-archive.com/pth-users@gnu.org/. Although the author tries hard to give the best support which is possible in his remaining free time, there cannot be any guarranty for help, because the author is a very busy hacker. So in your own interest: If you need help in case of a hard problems, keep your mail _VERY SHORT_ and _CONCISE_ and clearly mention your operating system, your way you have configured and built Pth and provide a way to _EASILY_ reproduce the problem. Don't die of laughter here - you would be terrified if you would know how much people of the authors software packages want help, but do not even mention the actual problem :-( Additionally in case of `segfaults' or other heavy problems, it is important that you provide the author a stack frame backtrace (see gdb's `bt' command) to allow the author to locate the problem. Without this information it is usually not possible to help you in case of such problems. Please understand, that you're not the only user of Pth and that Pth is not the only software package written by the author. So it is always appreciated that you first investigate yourself in solving the problem. If your problem then still remains, follow the above hints and contact the author. But please also understand, that application problems related to programming with Pth and the multithreaded paradigm cannot always be treated as real `problems'.