[jira] [Updated] (TS-1119) fatal error when uploading gzip-transform plugin
[
https://issues.apache.org/jira/browse/TS-1119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
angela asher updated TS-1119:
-
Priority: Blocker (was: Major)
fatal error when uploading gzip-transform plugin
Key: TS-1119
URL: https://issues.apache.org/jira/browse/TS-1119
Project: Traffic Server
Issue Type: Bug
Components: Plugins
Affects Versions: 3.0.2
Reporter: angela asher
Priority: Blocker
getting the following error on traffic.out when running the traffic server
with gzip-transform plugin:
[Feb 23 16:28:15.509] Server {47392853811680} DEBUG: (http) [13] calling
plugin on hook TS_HTTP_READ_RESPONSE_HDR_HOOK at hook 0x35BBEE0
FATAL: InkAPI.cc:3036: failed assert `sdk_sanity_check_null_ptr((void*)
value_len_ptr) == TS_SUCCESS`
/usr/local/bin/traffic_server - STACK TRACE:
/usr/local/lib/libtsutil.so.3(ink_fatal_va+0x9d)[0x2b1a7ecca37d]
/usr/local/lib/libtsutil.so.3(ink_fatal+0x88)[0x2b1a7ecca4d8]
/usr/local/lib/libtsutil.so.3(_ink_assert+0x85)[0x2b1a7ecc8af5]
/usr/local/bin/traffic_server(TSMimeHdrFieldValueStringGet+0x124)[0x4a9144]
/usr/local/libexec/trafficserver/gzip-transform.so(+0x1bde)[0x2b1a8b3c7bde]
/usr/local/libexec/trafficserver/gzip-transform.so(+0x27c4)[0x2b1a8b3c87c4]
/usr/local/bin/traffic_server(_ZN6HttpSM17state_api_calloutEiPv+0x525)[0x52cfa5]
/usr/local/bin/traffic_server(_ZN6HttpSM33state_read_server_response_headerEiPv+0x420)[0x52f1c0]
/usr/local/bin/traffic_server(_ZN6HttpSM12main_handlerEiPv+0xe8)[0x530568]
/usr/local/bin/traffic_server[0x681dcb]
/usr/local/bin/traffic_server[0x6848f1]
/usr/local/bin/traffic_server(_ZN10NetHandler12mainNetEventEiP5Event+0x2e2)[0x67d402]
/usr/local/bin/traffic_server(_ZN7EThread13process_eventEP5Eventi+0xb4)[0x6a9ce4]
/usr/local/bin/traffic_server(_ZN7EThread7executeEv+0x4c3)[0x6aa673]
/usr/local/bin/traffic_server(main+0x1128)[0x4c07e8]
/lib64/libc.so.6(__libc_start_main+0xfd)[0x2b1a81092c5d]
/usr/local/bin/traffic_server[0x47e0e9]
[Feb 23 16:28:15.512] Manager {140400187066336} ERROR:
[LocalManager::pollMgmtProcessServer] Server Process terminated due to Sig 6:
Aborted
[Feb 23 16:28:15.512] Manager {140400187066336} ERROR: (last system error 2:
No such file or directory)
[Feb 23 16:28:15.512] Manager {140400187066336} ERROR: [Alarms::signalAlarm]
Server Process was reset
[Feb 23 16:28:15.512] Manager {140400187066336} ERROR: (last system error 2:
No such file or directory)
[Feb 23 16:28:16.522] Manager {140400187066336} NOTE:
[LocalManager::startProxy] Launching ts process
[TrafficServer] using root directory '/usr/local'
[Feb 23 16:28:16.527] Manager {140400187066336} NOTE:
[LocalManager::pollMgmtProcessServer] New process connecting fd '11'
[Feb 23 16:28:16.527] Manager {140400187066336} NOTE: [Alarms::signalAlarm]
Server Process born
[Feb 23 16:28:17.539] {47668265021920} STATUS: opened
/usr/local/var/log/trafficserver/diags.log
[Feb 23 16:28:17.539] {47668265021920} NOTE: updated diags config
[Feb 23 16:28:17.541] Server {47668265021920} DEBUG: (http_aeua)
[HttpConfig::init_aeua_filter] - Config:
/usr/local/etc/trafficserver/ae_ua.config
[Feb 23 16:28:17.541] Server {47668265021920} DEBUG: (http_aeua)
[HttpConfig::init_aeua_filter] - Opening config
/usr/local/etc/trafficserver/ae_ua.config
[Feb 23 16:28:17.541] Server {47668265021920} DEBUG: (http_aeua)
[HttpConfig::init_aeua_filter] - Added 0 REGEXP filters
[Feb 23 16:28:17.541] Server {47668265021920} DEBUG: (http_aeua)
[init_http_aeua_filter] - Total loaded 0 REGEXP for
Accept-Enconding/User-Agent filtering
[Feb 23 16:28:17.542] Server {47668265021920} NOTE: cache clustering disabled
[Feb 23 16:28:17.543] Server {47668265021920} DEBUG: (dns) ink_dns_init:
called with init_called = 0
[Feb 23 16:28:17.546] Server {47668265021920} DEBUG: (dns)
localhost=isk-vsrv227
[Feb 23 16:28:17.546] Server {47668265021920} DEBUG: (dns) Round-robin
nameservers = 0
[Feb 23 16:28:17.547] Server {47668265021920} NOTE: cache clustering disabled
[Feb 23 16:28:17.568] Server {47668265021920} NOTE: logging initialized[7],
logging_mode = 3
[Feb 23 16:28:17.569] Server {47668265021920} NOTE: loading plugin
'/usr/local/libexec/trafficserver/gzip-transform.so'
[Feb 23 16:28:17.570] Server {47668265021920} DEBUG: (http_init)
proxy.config.http.redirection_enabled = 0
[Feb 23 16:28:17.570] Server {47668265021920} DEBUG: (http_init)
proxy.config.http.number_of_redirections = 1
[Feb 23 16:28:17.570] Server {47668265021920} DEBUG: (http_init)
proxy.config.http.post_copy_size = 2048
[Feb 23 16:28:17.570] Server {47668265021920} DEBUG: (http_tproxy) Primary
listen socket transparency is off
[Feb 23 16:28:17.573] Server {47668424926976} DEBUG: (http_tproxy) Marking
accepted connect on 39e0f80 as not outbound
[jira] [Commented] (TS-1120) Use ink_zero / ats_zero instead of calling memset when zeroing a variable or member.
[ https://issues.apache.org/jira/browse/TS-1120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13216805#comment-13216805 ] Alan M. Carroll commented on TS-1120: - Examples: @code foo bar; // value. ink_zero(bar); // zero bar. foo *bar; // pointer. ink_zero(bar); // WRONG - makes the pointer @a bar zero. ink_zero(*bar); // zero what bar points at. foo bar[ZOMG]; // Array of structs. ink_zero(bar); // Zero all structs in array. foo *bar[ZOMG]; // array of pointers. ink_zero(bar); // zero all pointers in the array. @endcode Use ink_zero / ats_zero instead of calling memset when zeroing a variable or member. Key: TS-1120 URL: https://issues.apache.org/jira/browse/TS-1120 Project: Traffic Server Issue Type: Improvement Components: Cleanup Affects Versions: 3.1.2 Reporter: Alan M. Carroll Priority: Minor Labels: cleanup, memory, safety Fix For: sometime We have an inline template, ink_zero(foo) which does memset(foo, 0, sizeof(foo)). Because this is easy to mess up with a typo, the inline template should be used for safety and clarity. Also, the template should be renamed ats_zero to be consistent. -- 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-1120) Use ink_zero / ats_zero instead of calling memset when zeroing a variable or member.
[
https://issues.apache.org/jira/browse/TS-1120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13216805#comment-13216805
]
Alan M. Carroll edited comment on TS-1120 at 2/26/12 6:44 PM:
--
{code:title=Examples}
foo bar; // value.
ink_zero(bar); // zero bar.
foo *bar; // pointer.
ink_zero(bar); // WRONG - makes the pointer @a bar zero.
ink_zero(*bar); // zero what bar points at.
foo bar[ZOMG]; // Array of structs.
ink_zero(bar); // Zero all structs in array.
foo *bar[ZOMG]; // array of pointers.
ink_zero(bar); // zero all pointers in the array.
{code}
was (Author: amc):
Examples:
[code]
foo bar; // value.
ink_zero(bar); // zero bar.
foo *bar; // pointer.
ink_zero(bar); // WRONG - makes the pointer @a bar zero.
ink_zero(*bar); // zero what bar points at.
foo bar[ZOMG]; // Array of structs.
ink_zero(bar); // Zero all structs in array.
foo *bar[ZOMG]; // array of pointers.
ink_zero(bar); // zero all pointers in the array.
[/code]
Use ink_zero / ats_zero instead of calling memset when zeroing a variable or
member.
Key: TS-1120
URL: https://issues.apache.org/jira/browse/TS-1120
Project: Traffic Server
Issue Type: Improvement
Components: Cleanup
Affects Versions: 3.1.2
Reporter: Alan M. Carroll
Priority: Minor
Labels: cleanup, memory, safety
Fix For: sometime
We have an inline template, ink_zero(foo) which does memset(foo, 0,
sizeof(foo)). Because this is easy to mess up with a typo, the inline
template should be used for safety and clarity. Also, the template should be
renamed ats_zero to be consistent.
--
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-1120) Use ink_zero / ats_zero instead of calling memset when zeroing a variable or member.
[
https://issues.apache.org/jira/browse/TS-1120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13216805#comment-13216805
]
Alan M. Carroll edited comment on TS-1120 at 2/26/12 6:45 PM:
--
{code:title=Examples}
foo bar; // value.
ink_zero(bar); // zero bar.
foo *bar; // pointer.
ink_zero(bar); // WRONG - makes the pointer @a bar zero.
ink_zero(*bar); // zero what bar points at.
foo bar[ZOMG]; // Array of structs.
ink_zero(bar); // Zero all structs in array.
foo *bar[ZOMG]; // array of pointers.
ink_zero(bar); // zero all pointers in the array.
{code}
was (Author: amc):
{code:title=Examples}
foo bar; // value.
ink_zero(bar); // zero bar.
foo *bar; // pointer.
ink_zero(bar); // WRONG - makes the pointer @a bar zero.
ink_zero(*bar); // zero what bar points at.
foo bar[ZOMG]; // Array of structs.
ink_zero(bar); // Zero all structs in array.
foo *bar[ZOMG]; // array of pointers.
ink_zero(bar); // zero all pointers in the array.
{code}
Use ink_zero / ats_zero instead of calling memset when zeroing a variable or
member.
Key: TS-1120
URL: https://issues.apache.org/jira/browse/TS-1120
Project: Traffic Server
Issue Type: Improvement
Components: Cleanup
Affects Versions: 3.1.2
Reporter: Alan M. Carroll
Priority: Minor
Labels: cleanup, memory, safety
Fix For: sometime
We have an inline template, ink_zero(foo) which does memset(foo, 0,
sizeof(foo)). Because this is easy to mess up with a typo, the inline
template should be used for safety and clarity. Also, the template should be
renamed ats_zero to be consistent.
--
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-1120) Use ink_zero / ats_zero instead of calling memset when zeroing a variable or member.
[
https://issues.apache.org/jira/browse/TS-1120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13216805#comment-13216805
]
Alan M. Carroll edited comment on TS-1120 at 2/26/12 6:46 PM:
--
{code:title=Examples}
// because formatting code eats all subsequent white space.
foo bar; // value.
ink_zero(bar); // zero bar.
foo *bar; // pointer.
ink_zero(bar); // WRONG - makes the pointer @a bar zero.
ink_zero(*bar); // zero what bar points at.
foo bar[ZOMG]; // Array of structs.
ink_zero(bar); // Zero all structs in array.
foo *bar[ZOMG]; // array of pointers.
ink_zero(bar); // zero all pointers in the array.
{code}
was (Author: amc):
{code:title=Examples}
foo bar; // value.
ink_zero(bar); // zero bar.
foo *bar; // pointer.
ink_zero(bar); // WRONG - makes the pointer @a bar zero.
ink_zero(*bar); // zero what bar points at.
foo bar[ZOMG]; // Array of structs.
ink_zero(bar); // Zero all structs in array.
foo *bar[ZOMG]; // array of pointers.
ink_zero(bar); // zero all pointers in the array.
{code}
Use ink_zero / ats_zero instead of calling memset when zeroing a variable or
member.
Key: TS-1120
URL: https://issues.apache.org/jira/browse/TS-1120
Project: Traffic Server
Issue Type: Improvement
Components: Cleanup
Affects Versions: 3.1.2
Reporter: Alan M. Carroll
Priority: Minor
Labels: cleanup, memory, safety
Fix For: sometime
We have an inline template, ink_zero(foo) which does memset(foo, 0,
sizeof(foo)). Because this is easy to mess up with a typo, the inline
template should be used for safety and clarity. Also, the template should be
renamed ats_zero to be consistent.
--
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-1120) Use ink_zero / ats_zero instead of calling memset when zeroing a variable or member.
[
https://issues.apache.org/jira/browse/TS-1120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13216805#comment-13216805
]
Alan M. Carroll edited comment on TS-1120 at 2/26/12 6:45 PM:
--
{code:title=Examples}
foo bar; // value.
ink_zero(bar); // zero bar.
foo *bar; // pointer.
ink_zero(bar); // WRONG - makes the pointer @a bar zero.
ink_zero(*bar); // zero what bar points at.
foo bar[ZOMG]; // Array of structs.
ink_zero(bar); // Zero all structs in array.
foo *bar[ZOMG]; // array of pointers.
ink_zero(bar); // zero all pointers in the array.
{code}
was (Author: amc):
{code:title=Examples}
foo bar; // value.
ink_zero(bar); // zero bar.
foo *bar; // pointer.
ink_zero(bar); // WRONG - makes the pointer @a bar zero.
ink_zero(*bar); // zero what bar points at.
foo bar[ZOMG]; // Array of structs.
ink_zero(bar); // Zero all structs in array.
foo *bar[ZOMG]; // array of pointers.
ink_zero(bar); // zero all pointers in the array.
{code}
Use ink_zero / ats_zero instead of calling memset when zeroing a variable or
member.
Key: TS-1120
URL: https://issues.apache.org/jira/browse/TS-1120
Project: Traffic Server
Issue Type: Improvement
Components: Cleanup
Affects Versions: 3.1.2
Reporter: Alan M. Carroll
Priority: Minor
Labels: cleanup, memory, safety
Fix For: sometime
We have an inline template, ink_zero(foo) which does memset(foo, 0,
sizeof(foo)). Because this is easy to mess up with a typo, the inline
template should be used for safety and clarity. Also, the template should be
renamed ats_zero to be consistent.
--
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-1120) Use ink_zero / ats_zero instead of calling memset when zeroing a variable or member.
[
https://issues.apache.org/jira/browse/TS-1120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13216805#comment-13216805
]
Alan M. Carroll edited comment on TS-1120 at 2/26/12 6:45 PM:
--
{code:title=Examples}
//
foo bar; // value.
ink_zero(bar); // zero bar.
foo *bar; // pointer.
ink_zero(bar); // WRONG - makes the pointer @a bar zero.
ink_zero(*bar); // zero what bar points at.
foo bar[ZOMG]; // Array of structs.
ink_zero(bar); // Zero all structs in array.
foo *bar[ZOMG]; // array of pointers.
ink_zero(bar); // zero all pointers in the array.
{code}
was (Author: amc):
{code:title=Examples}
foo bar; // value.
ink_zero(bar); // zero bar.
foo *bar; // pointer.
ink_zero(bar); // WRONG - makes the pointer @a bar zero.
ink_zero(*bar); // zero what bar points at.
foo bar[ZOMG]; // Array of structs.
ink_zero(bar); // Zero all structs in array.
foo *bar[ZOMG]; // array of pointers.
ink_zero(bar); // zero all pointers in the array.
{code}
Use ink_zero / ats_zero instead of calling memset when zeroing a variable or
member.
Key: TS-1120
URL: https://issues.apache.org/jira/browse/TS-1120
Project: Traffic Server
Issue Type: Improvement
Components: Cleanup
Affects Versions: 3.1.2
Reporter: Alan M. Carroll
Priority: Minor
Labels: cleanup, memory, safety
Fix For: sometime
We have an inline template, ink_zero(foo) which does memset(foo, 0,
sizeof(foo)). Because this is easy to mess up with a typo, the inline
template should be used for safety and clarity. Also, the template should be
renamed ats_zero to be consistent.
--
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-1120) Use ink_zero / ats_zero instead of calling memset when zeroing a variable or member.
[
https://issues.apache.org/jira/browse/TS-1120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13216805#comment-13216805
]
Alan M. Carroll edited comment on TS-1120 at 2/26/12 6:45 PM:
--
{code:title=Examples}
foo bar; // value.
ink_zero(bar); // zero bar.
foo *bar; // pointer.
ink_zero(bar); // WRONG - makes the pointer @a bar zero.
ink_zero(*bar); // zero what bar points at.
foo bar[ZOMG]; // Array of structs.
ink_zero(bar); // Zero all structs in array.
foo *bar[ZOMG]; // array of pointers.
ink_zero(bar); // zero all pointers in the array.
{code}
was (Author: amc):
{code:title=Examples}
//
foo bar; // value.
ink_zero(bar); // zero bar.
foo *bar; // pointer.
ink_zero(bar); // WRONG - makes the pointer @a bar zero.
ink_zero(*bar); // zero what bar points at.
foo bar[ZOMG]; // Array of structs.
ink_zero(bar); // Zero all structs in array.
foo *bar[ZOMG]; // array of pointers.
ink_zero(bar); // zero all pointers in the array.
{code}
Use ink_zero / ats_zero instead of calling memset when zeroing a variable or
member.
Key: TS-1120
URL: https://issues.apache.org/jira/browse/TS-1120
Project: Traffic Server
Issue Type: Improvement
Components: Cleanup
Affects Versions: 3.1.2
Reporter: Alan M. Carroll
Priority: Minor
Labels: cleanup, memory, safety
Fix For: sometime
We have an inline template, ink_zero(foo) which does memset(foo, 0,
sizeof(foo)). Because this is easy to mess up with a typo, the inline
template should be used for safety and clarity. Also, the template should be
renamed ats_zero to be consistent.
--
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-1120) Use ink_zero / ats_zero instead of calling memset when zeroing a variable or member.
[
https://issues.apache.org/jira/browse/TS-1120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13216805#comment-13216805
]
Alan M. Carroll edited comment on TS-1120 at 2/26/12 6:46 PM:
--
{code:title=Examples}
// because formatting code eats all subsequent white space
// you can't indent the first line.
foo bar; // value.
ink_zero(bar); // zero bar.
foo *bar; // pointer.
ink_zero(bar); // WRONG - makes the pointer @a bar zero.
ink_zero(*bar); // zero what bar points at.
foo bar[ZOMG]; // Array of structs.
ink_zero(bar); // Zero all structs in array.
foo *bar[ZOMG]; // array of pointers.
ink_zero(bar); // zero all pointers in the array.
{code}
was (Author: amc):
{code:title=Examples}
// because formatting code eats all subsequent white space.
foo bar; // value.
ink_zero(bar); // zero bar.
foo *bar; // pointer.
ink_zero(bar); // WRONG - makes the pointer @a bar zero.
ink_zero(*bar); // zero what bar points at.
foo bar[ZOMG]; // Array of structs.
ink_zero(bar); // Zero all structs in array.
foo *bar[ZOMG]; // array of pointers.
ink_zero(bar); // zero all pointers in the array.
{code}
Use ink_zero / ats_zero instead of calling memset when zeroing a variable or
member.
Key: TS-1120
URL: https://issues.apache.org/jira/browse/TS-1120
Project: Traffic Server
Issue Type: Improvement
Components: Cleanup
Affects Versions: 3.1.2
Reporter: Alan M. Carroll
Priority: Minor
Labels: cleanup, memory, safety
Fix For: sometime
We have an inline template, ink_zero(foo) which does memset(foo, 0,
sizeof(foo)). Because this is easy to mess up with a typo, the inline
template should be used for safety and clarity. Also, the template should be
renamed ats_zero to be consistent.
--
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-1122) Make regex_remap plugin understand redirect directives
[ https://issues.apache.org/jira/browse/TS-1122?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13217021#comment-13217021 ] Leif Hedstrom commented on TS-1122: --- This should be fixed in 8a5e0f7b373c4cd82706895730373c88cc998acf. Make regex_remap plugin understand redirect directives -- Key: TS-1122 URL: https://issues.apache.org/jira/browse/TS-1122 Project: Traffic Server Issue Type: Improvement Components: Plugins Reporter: Leif Hedstrom Assignee: Leif Hedstrom Fix For: 3.1.3 Fix the code to support the new APIs, for dealing with redirects. -- 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] [Updated] (TS-1121) --disable-diags configuration option does not do anything
[ https://issues.apache.org/jira/browse/TS-1121?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leif Hedstrom updated TS-1121: -- Fix Version/s: 3.1.3 --disable-diags configuration option does not do anything - Key: TS-1121 URL: https://issues.apache.org/jira/browse/TS-1121 Project: Traffic Server Issue Type: Bug Components: Build, Core Affects Versions: 3.0.3 Environment: any Reporter: Uri Shachar Priority: Minor Fix For: 3.1.3 Original Estimate: 2h Remaining Estimate: 2h The --disable-diags flag sets TS_USE_DIAGS to 0 but Diags.h tests if it is defined or not -- 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-1109) stack dump may crash too
[ https://issues.apache.org/jira/browse/TS-1109?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13217056#comment-13217056 ] weijin commented on TS-1109: By disassembly ink_restore_signal_handler_frameļ¼ I found it was not the base frame address but the function args stored in %rbp in release mode. The embedded assembly codes of getting base frame address is dangerous and have poor portability, so I remove them from the sources. stack dump may crash too Key: TS-1109 URL: https://issues.apache.org/jira/browse/TS-1109 Project: Traffic Server Issue Type: Bug Components: Core Affects Versions: 3.1.2 Reporter: Zhao Yongming Assignee: weijin Labels: crash Fix For: 3.1.4 the codes doing stack dump may crash, in this case you will not able to get a core file, that will hide most of the rare issues. -- 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-1109) stack dump may crash too
[
https://issues.apache.org/jira/browse/TS-1109?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13217059#comment-13217059
]
weijin commented on TS-1109:
Breakpoint 1, ink_stack_trace_get (stack=0x7fffb4d0, len=100,
signalhandler_frame=2) at ink_stack_trace.cc:85
85 {
(gdb) n
87if ((btl = backtrace(stack, len)) 0) {
(gdb)
88 if (signalhandler_frame)
(gdb)
89ink_restore_signal_handler_frame(stack, btl, signalhandler_frame
+ 1);
(gdb) s
ink_restore_signal_handler_frame (stack=0x7fffb4d0, len=value optimized
out, signalhandler_frame=2) at ink_stack_trace.cc:63
63asm volatile (mov %%rbp,%0:=r (fp));
(gdb) info reg rbp
rbp0x2 0x2
(gdb) n
67for (i = 0; i signalhandler_frame; i++)
(gdb)
68 fp = (void **) (*fp);
(gdb)
Program received signal SIGSEGV, Segmentation fault.
stack dump may crash too
Key: TS-1109
URL: https://issues.apache.org/jira/browse/TS-1109
Project: Traffic Server
Issue Type: Bug
Components: Core
Affects Versions: 3.1.2
Reporter: Zhao Yongming
Assignee: weijin
Labels: crash
Fix For: 3.1.4
the codes doing stack dump may crash, in this case you will not able to get a
core file, that will hide most of the rare issues.
--
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] [Updated] (TS-1109) stack dump may crash too
[ https://issues.apache.org/jira/browse/TS-1109?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] weijin updated TS-1109: --- Attachment: cop_crash.diff stack dump may crash too Key: TS-1109 URL: https://issues.apache.org/jira/browse/TS-1109 Project: Traffic Server Issue Type: Bug Components: Core Affects Versions: 3.1.2 Reporter: Zhao Yongming Assignee: weijin Labels: crash Fix For: 3.1.4 Attachments: cop_crash.diff the codes doing stack dump may crash, in this case you will not able to get a core file, that will hide most of the rare issues. -- 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] [Work started] (TS-1109) stack dump may crash too
[ https://issues.apache.org/jira/browse/TS-1109?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on TS-1109 started by weijin. stack dump may crash too Key: TS-1109 URL: https://issues.apache.org/jira/browse/TS-1109 Project: Traffic Server Issue Type: Bug Components: Core Affects Versions: 3.1.2 Reporter: Zhao Yongming Assignee: weijin Labels: crash Fix For: 3.1.4 Attachments: cop_crash.diff the codes doing stack dump may crash, in this case you will not able to get a core file, that will hide most of the rare issues. -- 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] [Work stopped] (TS-1109) stack dump may crash too
[ https://issues.apache.org/jira/browse/TS-1109?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on TS-1109 stopped by weijin. stack dump may crash too Key: TS-1109 URL: https://issues.apache.org/jira/browse/TS-1109 Project: Traffic Server Issue Type: Bug Components: Core Affects Versions: 3.1.2 Reporter: Zhao Yongming Assignee: weijin Labels: crash Fix For: 3.1.4 Attachments: cop_crash.diff the codes doing stack dump may crash, in this case you will not able to get a core file, that will hide most of the rare issues. -- 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] [Updated] (TS-1109) stack dump may crash too
[ https://issues.apache.org/jira/browse/TS-1109?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhao Yongming updated TS-1109: -- Fix Version/s: (was: 3.1.4) 3.1.3 stack dump may crash too Key: TS-1109 URL: https://issues.apache.org/jira/browse/TS-1109 Project: Traffic Server Issue Type: Bug Components: Core Affects Versions: 3.1.2 Reporter: Zhao Yongming Assignee: weijin Labels: crash Fix For: 3.1.3 Attachments: cop_crash.diff the codes doing stack dump may crash, in this case you will not able to get a core file, that will hide most of the rare issues. -- 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-1112) traffic_cop may crash at free()
[ https://issues.apache.org/jira/browse/TS-1112?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13217064#comment-13217064 ] weijin commented on TS-1112: I am not sure why this happen, and it did not arise since another problem solved. So maybe we can close it now, and reopen it if it arise again. traffic_cop may crash at free() --- Key: TS-1112 URL: https://issues.apache.org/jira/browse/TS-1112 Project: Traffic Server Issue Type: Bug Environment: v3.0.x Reporter: Zhao Yongming Assignee: weijin Fix For: 3.1.4 traffic_cop may crash, at memory free, that will leave the manager server alone, or may die with the manager too, leave a system without service. -- 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
