bryancall opened a new issue, #11588:
URL: https://github.com/apache/trafficserver/issues/11588

   I saw this crash 2 times in the last day:
   ```
   (gdb) bt
   #0  0x00007ff7fb532acf in raise () from /lib64/libc.so.6
   #1  0x00007ff7fb505ea5 in abort () from /lib64/libc.so.6
   #2  0x00007ff7fd0e2a4b in ink_abort 
(message_format=message_format@entry=0x7ff7fd0f5bef "%s:%d: failed assertion 
`%s`")
       at 
/sd/workspace/src/git.ouryahoo.com/Edge/build/_scm/trafficserver10.0/src/tscore/ink_error.cc:99
   #3  0x00007ff7fd0df425 in _ink_assert (expression=expression@entry=0x8fd040 
"name_len + value_len <= this->_capacity",
       file=file@entry=0x8fcf88 
"/sd/workspace/src/git.ouryahoo.com/Edge/build/_scm/trafficserver10.0/src/proxy/hdrs/XPACK.cc",
 line=line@entry=568)
       at 
/sd/workspace/src/git.ouryahoo.com/Edge/build/_scm/trafficserver10.0/src/tscore/ink_assert.cc:35
   #4  0x00000000006baa1e in XpackDynamicTableStorage::write (this=<optimized 
out>, name=<optimized out>, name_len=4, value=<optimized out>, 
value_len=<optimized out>)
       at 
/sd/workspace/src/git.ouryahoo.com/Edge/build/_scm/trafficserver10.0/src/proxy/hdrs/XPACK.cc:568
   #5  0x00000000006bab80 in XpackDynamicTable::insert_entry 
(this=0x7fed18aacd38, name=0x7ff7efdfb300 "linkent-typerity-policyty\b\212", 
name_len=4, value=0x7fe871ad8b14 "", value_len=18550)
       at 
/sd/workspace/src/git.ouryahoo.com/Edge/build/_scm/trafficserver10.0/src/proxy/hdrs/XPACK.cc:356
   #6  0x00000000006bad12 in XpackDynamicTable::insert_entry 
(value_len=<optimized out>, value=<optimized out>, name_len=<optimized out>, 
name=<optimized out>, this=<optimized out>)
       at 
/sd/workspace/src/git.ouryahoo.com/Edge/build/_scm/trafficserver10.0/src/proxy/hdrs/XPACK.cc:338
   ```


-- 
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: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to