bneradt opened a new issue, #11700:
URL: https://github.com/apache/trafficserver/issues/11700
We're seeing a crash related to an interaction between cache and handling
redirects:
```gdb
#0 0x0000000000587c7d in HttpSM::setup_cache_write_transfer (name=0x8e1ab5
"cache write", skip_bytes=1395, store_info=0x7fa31d298180,
source_vc=0x7fadc0aedc90, c_sm=0x7fa31d29a430, this=0x7fa31d298000)
at
/sd/workspace/src/git.ouryahoo.com/Edge/build/_scm/trafficserver10.0/src/proxy/http/HttpSM.cc:6770
#1 HttpSM::perform_cache_write_action (this=this@entry=0x7fa31d298000) at
/sd/workspace/src/git.ouryahoo.com/Edge/build/_scm/trafficserver10.0/src/proxy/http/HttpSM.cc:6425
#2 0x000000000059d25e in HttpSM::handle_api_return (this=0x7fa31d298000) at
/sd/workspace/src/git.ouryahoo.com/Edge/build/_scm/trafficserver10.0/src/proxy/http/HttpSM.cc:1630
#3 0x000000000059731e in HttpSM::state_api_callout (this=0x7fa31d298000,
event=<optimized out>) at
/sd/workspace/src/git.ouryahoo.com/Edge/build/_scm/trafficserver10.0/src/proxy/http/HttpSM.cc:1491
#4 0x000000000059e4a6 in HttpSM::state_api_callback
(this=this@entry=0x7fa31d298000, event=event@entry=60000, data=data@entry=0x0)
at
/sd/workspace/src/git.ouryahoo.com/Edge/build/_scm/trafficserver10.0/src/proxy/http/HttpSM.cc:1295
#5 0x00007fadce570813 in TSHttpTxnReenable (txnp=0x7fa31d298000,
event=TS_EVENT_HTTP_CONTINUE) at
/sd/workspace/src/git.ouryahoo.com/Edge/build/_scm/trafficserver10.0/src/api/InkAPI.cc:4935
#6 0x00007fac5029cc76 in ?? ()
#7 0x00007fa31d298000 in ?? ()
#8 0x00007fa81fcac1c0 in ?? ()
#9 0x0000000000000000 in ?? ()
```
Some interesting variables @JosiahWI asked me to look at:
```gdb
(gdb) p t_state.redirect_info.redirect_in_process
$1 = true
(gdb) f 1
(gdb) p t_state.cache_info.action
$2 = HttpTransact::CACHE_DO_WRITE
```
--
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.
To unsubscribe, e-mail: issues-unsubscr...@trafficserver.apache.org.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
