https://issues.apache.org/bugzilla/show_bug.cgi?id=48811

--- Comment #5 from Jeff Trawick <[email protected]> 2010-02-25 19:03:44 UTC 
---
>reboot
>reverse order -- app2, then app1.  same result, now - both display OK, no error
>msgs.

>confusion?

I suspect that the insertion of debug code has worked around some undesired
code generation.

Here's the crucial logic in modules/fcgid/fcgid_proctbl_unix.c to initialize
the free list where I inserted some debug code:

     ptmpnode = g_free_list_header;
     for (i = 0; i < FCGID_MAX_APPLICATION; i++) {
         ptmpnode->next_index = ptmpnode - g_proc_array + 1;
+        if (i < 4 || (i + 4) >= FCGID_MAX_APPLICATION) {
+            ap_log_error(APLOG_MARK, APLOG_DEBUG, 0, main_server,
+                         "free node %d at %d (prev node %pp)",
+                         i, ptmpnode->next_index, ptmpnode);
+        }
         ptmpnode++;
     }

Try editing modules/fcgid/fcgid_proctbl_unix.c to disable just the inserted
debug code there, compiling/installing, and trying the test again.  It should
look something like

     ptmpnode = g_free_list_header;
     for (i = 0; i < FCGID_MAX_APPLICATION; i++) {
         ptmpnode->next_index = ptmpnode - g_proc_array + 1;
 #if 0
         if (i < 4 || (i + 4) >= FCGID_MAX_APPLICATION) {
             ap_log_error(APLOG_MARK, APLOG_DEBUG, 0, main_server,
                          "free node %d at %d (prev node %pp)",
                          i, ptmpnode->next_index, ptmpnode);
         }
 #endif
         ptmpnode++;
     }


If that doesn't cause the bug to reappear, you'll probably need to try to
remove one call to log_free_list() at a time until the bug reappears or you're
back to the code in svn and/or we get really confused.

-- 
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to