You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@trafficserver.apache.org by "Conan Wang (Updated) (JIRA)" <ji...@apache.org> on 2011/12/26 20:32:30 UTC

[jira] [Updated] (TS-1065) traffic_cop segment fault when enable TRACE_LOG_COP

     [ https://issues.apache.org/jira/browse/TS-1065?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Conan Wang updated TS-1065:
---------------------------

    Attachment: traffic_cop.diff

diff tested on mac os 10.7.2 and centos 5.4 64bit.
                
> traffic_cop segment fault when enable TRACE_LOG_COP
> ---------------------------------------------------
>
>                 Key: TS-1065
>                 URL: https://issues.apache.org/jira/browse/TS-1065
>             Project: Traffic Server
>          Issue Type: Bug
>    Affects Versions: 3.1.1, 3.0.2
>         Environment: mac os 10.7.2, centos 5.4 64bit
>            Reporter: Conan Wang
>            Priority: Minor
>         Attachments: traffic_cop.diff
>
>
> When enable traffic_cop's debug log:  #define TRACE_LOG_COP 1 
> Some cop_log invocation will cause segment fault, because va_list object in cop_log is used twice between 'va_start' and 'va_end'.
> {code}
> Program received signal EXC_BAD_ACCESS, Could not access memory.
> Reason: KERN_INVALID_ADDRESS at address: 0x0000000000000000
> 0x00007fff846b64f0 in strlen ()
> (gdb) bt
> #0  0x00007fff846b64f0 in strlen ()
> #1  0x00007fff846578c3 in __vfprintf ()
> #2  0x00007fff846a109b in vsprintf_l ()
> #3  0x0000000100001883 in cop_log (priority=5, format=0x1000072a8 "--- Cop Starting [Version: %s] ---\n") at TrafficCop.cc:172
> #4  0x0000000100002244 in check_lockfile () at TrafficCop.cc:1733
> #5  0x00000001000022c0 in init () at TrafficCop.cc:1894
> #6  0x0000000100006689 in main (argc=1, argv=0x7fff5fbffbb0) at TrafficCop.cc:1958
> {code}
> Reference:
> http://pubs.opengroup.org/onlinepubs/009695399/basedefs/stdarg.h.html

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira