[ 
https://issues.apache.org/jira/browse/TS-832?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Leif Hedstrom updated TS-832:
-----------------------------

    Fix Version/s:     (was: 3.3.5)
                   3.3.6

Nothing happening here in a long time, so moving out. Is this still an issue?
                
> Crash Report: RecMessageMarshal_Realloc in cluster mode 2
> ---------------------------------------------------------
>
>                 Key: TS-832
>                 URL: https://issues.apache.org/jira/browse/TS-832
>             Project: Traffic Server
>          Issue Type: Bug
>          Components: Clustering, Core
>    Affects Versions: 3.1.0
>         Environment: version trunk, aka v3.0 after, cluster mode set to 2( 
> management cluster ), --enable-debug
>            Reporter: Zhao Yongming
>              Labels: cluster, realloc
>             Fix For: 3.3.6
>
>
> here is two core dumps:
> {code}
>     #0  0x0000003c33030265 in raise () from /lib64/libc.so.6
>     (gdb) bt
>     #0  0x0000003c33030265 in raise () from /lib64/libc.so.6
>     #1  0x0000003c33031d10 in abort () from /lib64/libc.so.6
>     #2  0x0000003c3306a84b in __libc_message () from /lib64/libc.so.6
>     #3  0x0000003c33075421 in realloc () from /lib64/libc.so.6
>     #4  0x00002acf28ff4e01 in ink_realloc (ptr=Could not find the frame base 
> for "ink_realloc".
>     ) at ink_memory.cc:88
>     #5  0x00000000006f2835 in RecMessageMarshal_Realloc (msg=0x2aaaab6d6010, 
> record=0x2acf29248f50) at RecMessage.cc:350
>     #6  0x00000000006eced8 in send_push_message () at P_RecCore.i:154
>     #7  0x00000000006efef9 in sync_cont::sync (this=0x20034150, event=1, 
> e=0x20033d30) at RecProcess.cc:263
>     #8  0x00000000004d2c5f in Continuation::handleEvent (this=0x20034150, 
> event=1, data=0x20033d30) at I_Continuation.h:146
>     #9  0x00000000006f5f0b in EThread::execute (this=0x2aaaab5d5010) at 
> UnixEThread.cc:287
>     #10 0x00000000006f5181 in spawn_thread_internal (a=0x200441b0) at 
> Thread.cc:88
>     #11 0x0000003c33c064a7 in start_thread () from /lib64/libpthread.so.0
>     #12 0x0000003c330d3c2d in clone () from /lib64/libc.so.6
>     (gdb) info f
>     Stack level 0, frame at 0x41f4c3e0:
>      rip = 0x3c33030265 in raise; saved rip 0x3c33031d10
>      called by frame at 0x41f4c520
>      Arglist at 0x41f4c3d0, args:
>      Locals at 0x41f4c3d0, Previous frame's sp is 0x41f4c3e0
>      Saved registers:
>       rip at 0x41f4c3d8
> {code}
> {code}
>     #0  0x00000038aa230265 in raise () from /lib64/libc.so.6
>     (gdb) bt
>     #0  0x00000038aa230265 in raise () from /lib64/libc.so.6
>     #1  0x00000038aa231d10 in abort () from /lib64/libc.so.6
>     #2  0x00000038aa26a84b in __libc_message () from /lib64/libc.so.6
>     #3  0x00000038aa275421 in realloc () from /lib64/libc.so.6
>     #4  0x00002ab28042ce01 in ink_realloc (ptr=Could not find the frame base 
> for "ink_realloc".
>     ) at ink_memory.cc:88
>     #5  0x00000000006f2835 in RecMessageMarshal_Realloc (msg=0x2aaaab6d6010, 
> record=0x2ab280680f50) at RecMessage.cc:350
>     #6  0x00000000006eced8 in send_push_message () at P_RecCore.i:154
>     #7  0x00000000006efef9 in sync_cont::sync (this=0x16a6f150, event=1, 
> e=0x16a6ed30) at RecProcess.cc:263
>     #8  0x00000000004d2c5f in Continuation::handleEvent (this=0x16a6f150, 
> event=1, data=0x16a6ed30) at I_Continuation.h:146
>     #9  0x00000000006f5f0b in EThread::execute (this=0x2aaaab5d5010) at 
> UnixEThread.cc:287
>     #10 0x00000000006f5181 in spawn_thread_internal (a=0x16a7f1b0) at 
> Thread.cc:88
>     #11 0x00000038aae064a7 in start_thread () from /lib64/libpthread.so.0
>     #12 0x00000038aa2d3c2d in clone () from /lib64/libc.so.6
>     (gdb) info f
>     Stack level 0, frame at 0x406b03e0:
>      rip = 0x38aa230265 in raise; saved rip 0x38aa231d10
>      called by frame at 0x406b0520
>      Arglist at 0x406b03d0, args:
>      Locals at 0x406b03d0, Previous frame's sp is 0x406b03e0
>      Saved registers:
>       rip at 0x406b03d8
> {code}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to