[jira] [Created] (TS-1201) Crash report: hostdb multicache, double free
Crash report: hostdb multicache, double free
Key: TS-1201
URL: https://issues.apache.org/jira/browse/TS-1201
Project: Traffic Server
Issue Type: Bug
Reporter: Zhao Yongming
Assignee: weijin
{code}
*** glibc detected *** /usr/bin/traffic_server: corrupted double-linked list:
0x1fe10ef0 ***
=== Backtrace: =
/lib64/libc.so.6[0x3db2072555]
/lib64/libc.so.6(cfree+0x4b)[0x3db20728bb]
/usr/bin/traffic_server(_ZN14MultiCacheSync7mcEventEiP5Event+0xa4)[0x5dae04]
/usr/bin/traffic_server(_ZN7EThread13process_eventEP5Eventi+0x22f)[0x691c8f]
/usr/bin/traffic_server(_ZN7EThread7executeEv+0x6a1)[0x692681]
/usr/bin/traffic_server[0x69115e]
/lib64/libpthread.so.0[0x3db280673d]
/lib64/libc.so.6(clone+0x6d)[0x3db20d44bd]
=== Memory map:
{code}
--
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
[jira] [Commented] (TS-1116) Fix build issues with clang (particularly on OSX)
[ https://issues.apache.org/jira/browse/TS-1116?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13252973#comment-13252973 ] Igor Galić commented on TS-1116: Brian, I only added the SHAs which seemed sensible. The one for configure.in to add -Werror didn't seem useful for this particular bug. > Fix build issues with clang (particularly on OSX) > - > > Key: TS-1116 > URL: https://issues.apache.org/jira/browse/TS-1116 > Project: Traffic Server > Issue Type: Improvement >Affects Versions: 3.0.4, 3.0.3 >Reporter: Leif Hedstrom >Assignee: Brian Geffon > Fix For: 3.1.3 > > Attachments: TS-1116.diff > > > We should get it to compile with clang again, specially since on OSX, clang > is the 'future'. -- 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
[jira] [Assigned] (TS-857) Crash Report: HttpTunnel::chain_abort_all -> HttpServerSession::do_io_close -> UnixNetVConnection::do_io_close
[
https://issues.apache.org/jira/browse/TS-857?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brian Geffon reassigned TS-857:
---
Assignee: Brian Geffon (was: weijin)
> Crash Report: HttpTunnel::chain_abort_all -> HttpServerSession::do_io_close
> -> UnixNetVConnection::do_io_close
> --
>
> Key: TS-857
> URL: https://issues.apache.org/jira/browse/TS-857
> Project: Traffic Server
> Issue Type: Bug
> Components: HTTP, Network
>Affects Versions: 3.1.0
> Environment: in my branch that is something same as 3.0.x
>Reporter: Zhao Yongming
>Assignee: Brian Geffon
> Fix For: 3.1.4
>
> Attachments: TS-857-jp1.patch, locking-jp1.patch, ts-857.diff,
> ts-857.diff, ts-857.diff
>
>
> here is the bt from the crash, some of the information is missing due to we
> have not enable the --enable-debug configure options.
> {code}
> [New process 7532]
> #0 ink_stack_trace_get (stack=, len= out>, signalhandler_frame=)
> at ink_stack_trace.cc:68
> 68fp = (void **) (*fp);
> (gdb) bt
> #0 ink_stack_trace_get (stack=, len= out>, signalhandler_frame=)
> at ink_stack_trace.cc:68
> #1 0x2ba641dccef1 in ink_stack_trace_dump (sighandler_frame= optimized out>) at ink_stack_trace.cc:114
> #2 0x004df020 in signal_handler (sig=) at
> signals.cc:225
> #3
> #4 0x006a1ea9 in UnixNetVConnection::do_io_close (this=0x1cc9bd20,
> alerrno=)
> at ../../iocore/eventsystem/I_Lock.h:297
> #5 0x0051f1d0 in HttpServerSession::do_io_close
> (this=0x2aaab0042c80, alerrno=20600) at HttpServerSession.cc:127
> #6 0x0056d1e9 in HttpTunnel::chain_abort_all (this=0x2aabeeffdd70,
> p=0x2aabeeffdf68) at HttpTunnel.cc:1300
> #7 0x005269ca in HttpSM::tunnel_handler_ua (this=0x2aabeeffc070,
> event=104, c=0x2aabeeffdda8) at HttpSM.cc:2987
> #8 0x00571dfc in HttpTunnel::consumer_handler (this=0x2aabeeffdd70,
> event=104, c=0x2aabeeffdda8) at HttpTunnel.cc:1232
> #9 0x00572032 in HttpTunnel::main_handler (this=0x2aabeeffdd70,
> event=1088608784, data=)
> at HttpTunnel.cc:1456
> #10 0x006a6307 in write_to_net_io (nh=0x2b12d688, vc=0x1cc876e0,
> thread=)
> at ../../iocore/eventsystem/I_Continuation.h:146
> #11 0x0069ce97 in NetHandler::mainNetEvent (this=0x2b12d688,
> event=, e=0x171c1ed0) at UnixNet.cc:405
> #12 0x006cddaf in EThread::process_event (this=0x2b12c010,
> e=0x171c1ed0, calling_code=5) at I_Continuation.h:146
> #13 0x006ce6bc in EThread::execute (this=0x2b12c010) at
> UnixEThread.cc:262
> #14 0x006cd0ee in spawn_thread_internal (a=0x171b58f0) at Thread.cc:88
> #15 0x003c33c064a7 in start_thread () from /lib64/libpthread.so.0
> #16 0x003c330d3c2d in clone () from /lib64/libc.so.6
> (gdb) info f
> Stack level 0, frame at 0x40e2b790:
> rip = 0x2ba641dccdf3 in ink_stack_trace_get(void**, int, int)
> (ink_stack_trace.cc:68); saved rip 0x2ba641dccef1
> called by frame at 0x40e2bbe0
> source language c++.
> Arglist at 0x40e2b770, args: stack=, len= optimized out>, signalhandler_frame=
> Locals at 0x40e2b770, Previous frame's sp is 0x40e2b790
> Saved registers:
> rbx at 0x40e2b778, rbp at 0x40e2b780, rip at 0x40e2b788
> (gdb)
> {code}
--
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
[jira] [Commented] (TS-1116) Fix build issues with clang (particularly on OSX)
[ https://issues.apache.org/jira/browse/TS-1116?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13252951#comment-13252951 ] Brian Geffon commented on TS-1116: -- @Jan-Frode Myklebust: all that will be included in 3.0.5 will be the commits referenced in the STATUS file which is only fe1da80b94d368343174ada8b137a0c4ae1c387e. @Igor, should there be multiple SHAs in the STATUS file, should I be backporting based on your comment above / and or start a new vote? > Fix build issues with clang (particularly on OSX) > - > > Key: TS-1116 > URL: https://issues.apache.org/jira/browse/TS-1116 > Project: Traffic Server > Issue Type: Improvement >Affects Versions: 3.0.4, 3.0.3 >Reporter: Leif Hedstrom >Assignee: Brian Geffon > Fix For: 3.1.3 > > Attachments: TS-1116.diff > > > We should get it to compile with clang again, specially since on OSX, clang > is the 'future'. -- 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
[jira] [Issue Comment Edited] (TS-1116) Fix build issues with clang (particularly on OSX)
[ https://issues.apache.org/jira/browse/TS-1116?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13252764#comment-13252764 ] Brian Geffon edited comment on TS-1116 at 4/12/12 7:41 PM: --- Ok, i'll make the final vote for it and it will be included in 3.0.5. was (Author: briang): I'll get it added to STATUS so voting can start on it. > Fix build issues with clang (particularly on OSX) > - > > Key: TS-1116 > URL: https://issues.apache.org/jira/browse/TS-1116 > Project: Traffic Server > Issue Type: Improvement >Affects Versions: 3.0.4, 3.0.3 >Reporter: Leif Hedstrom >Assignee: Brian Geffon > Fix For: 3.1.3 > > Attachments: TS-1116.diff > > > We should get it to compile with clang again, specially since on OSX, clang > is the 'future'. -- 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
[jira] [Commented] (TS-1116) Fix build issues with clang (particularly on OSX)
[ https://issues.apache.org/jira/browse/TS-1116?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13252764#comment-13252764 ] Brian Geffon commented on TS-1116: -- I'll get it added to STATUS so voting can start on it. > Fix build issues with clang (particularly on OSX) > - > > Key: TS-1116 > URL: https://issues.apache.org/jira/browse/TS-1116 > Project: Traffic Server > Issue Type: Improvement >Affects Versions: 3.0.4, 3.0.3 >Reporter: Leif Hedstrom >Assignee: Brian Geffon > Fix For: 3.1.3 > > Attachments: TS-1116.diff > > > We should get it to compile with clang again, specially since on OSX, clang > is the 'future'. -- 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
[jira] [Resolved] (TS-1200) DOAP file reference incorrect
[ https://issues.apache.org/jira/browse/TS-1200?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebb resolved TS-1200. -- Resolution: Fixed Looks like the hack (r1325085) was sufficient, at least for this case. > DOAP file reference incorrect > - > > Key: TS-1200 > URL: https://issues.apache.org/jira/browse/TS-1200 > Project: Traffic Server > Issue Type: Bug >Reporter: Sebb >Assignee: Igor Galić >Priority: Critical > > The DOAP file for the project needs to be available for the projects.a.o > website to function correctly. > Currently the build is looking for > http://svn.apache.org/repos/asf/trafficserver/traffic/trunk/doc/doap.rdf > However this does not exist, so the build is reporting an error. > Please update the file > https://svn.apache.org/repos/asf/infrastructure/site-tools/trunk/projects/files.xml > with the new location ASAP. -- 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
[jira] [Commented] (TS-1116) Fix build issues with clang (particularly on OSX)
[ https://issues.apache.org/jira/browse/TS-1116?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13252322#comment-13252322 ] Jan-Frode Myklebust commented on TS-1116: - Brian, please see patch in TS-1185. I've cherry picked commit 9e3459a1006ad2e4381d20fe5374a11994dccf88 and cea3c71360a066a24b39e36ee116e83ea1db1bc8 into v3.0.4 to make it build on fedora-17 which has gcc-4.7. It would be great if you could include these patches in the upcoming v3.0.5 release. > Fix build issues with clang (particularly on OSX) > - > > Key: TS-1116 > URL: https://issues.apache.org/jira/browse/TS-1116 > Project: Traffic Server > Issue Type: Improvement >Affects Versions: 3.0.4, 3.0.3 >Reporter: Leif Hedstrom >Assignee: Brian Geffon > Fix For: 3.1.3 > > Attachments: TS-1116.diff > > > We should get it to compile with clang again, specially since on OSX, clang > is the 'future'. -- 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
