Vijay-1 commented on issue #4921:
URL: https://github.com/apache/trafficserver/issues/4921#issuecomment-747335286
@masaori335 @zwoop
Got this core in our production with 8.0.8
(gdb) bt
#0 0x00002b6d5a1a5337 in raise () from /lib64/libc.so.6
#1 0x00002b6d5a1a6a28 in abort () from /lib64/libc.so.6
#2 0x00002b6d57b85a1b in ink_abort
(message_format=message_format@entry=0x2b6d57c03c67 "%s:%d: failed assertion
`%s`") at ink_error.cc:99
#3 0x00002b6d57b82675 in _ink_assert (expression=expression@entry=0x76fc4e
"magic == HTTP_SM_MAGIC_ALIVE", file=file@entry=0x76f61e "HttpSM.cc",
line=line@entry=2516) at ink_assert.cc:37
#4 0x0000000000506107 in HttpSM::main_handler (this=<optimized out>,
event=<optimized out>, data=<optimized out>) at HttpSM.cc:2516
#5 0x0000000000555221 in handleEvent (data=0x2b6da013eeb0, event=2301,
this=<optimized out>)
at
/usr/src/debug/trafficserver-8.0.7/iocore/eventsystem/I_Continuation.h:160
#6 HttpTunnel::main_handler (this=0x2b6da013eeb0, event=<optimized out>,
data=<optimized out>) at HttpTunnel.cc:1692
#7 0x0000000000752bb2 in handleEvent (data=0x2b6d941fd020, event=103,
this=<optimized out>) at I_Continuation.h:160
#8 EThread::process_event (this=this@entry=0x2b6d61b3b010,
e=e@entry=0x2b6d941fd020, calling_code=103) at UnixEThread.cc:131
#9 0x000000000075347e in EThread::process_queue
(this=this@entry=0x2b6d61b3b010,
NegativeQueue=NegativeQueue@entry=0x2b6d7892ee70,
ev_count=ev_count@entry=0x2b6d7892ee6c,
nq_count=nq_count@entry=0x2b6d7892ee68) at UnixEThread.cc:170
#10 0x0000000000753a68 in EThread::execute_regular (this=0x2b6d61b3b010) at
UnixEThread.cc:230
#11 0x00000000007525aa in spawn_thread_internal (a=0x2a8ff60) at Thread.cc:85
#12 0x00002b6d59537e65 in start_thread () from /lib64/libpthread.so.0
#13 0x00002b6d5a26d88d in clone () from /lib64/libc.so.6
(gdb)
Was able to verify
[5934](https://github.com/apache/trafficserver/pull/5934). Back ported this to
8.0.8 and verified.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
