empiredan commented on issue #1848:
URL: 
https://github.com/apache/incubator-pegasus/issues/1848#issuecomment-1895567447

   > We upgraded the gperftools to 2.13 on the master branch recently, but I 
saw the stack it was using the lib in `/lib64/libtcmalloc_and_profiler.so.4`. 
Please check if there is any issue of the run.sh script.
   
   Yes, this problem relates to the linked shared object of tcmalloc, namely 
`libtcmalloc_and_profiler.so*`.
   
   In my environment, while replica server exited abnormally with coredump, I 
found that by `ldd bin/pegasus_server` it was always linked to 
`/lib64/libtcmalloc_and_profiler.so.4`, even if the libraries packed by 
[pack_server.sh](https://github.com/apache/incubator-pegasus/blob/master/scripts/pack_server.sh)
 were added in `LD_LIBRARY_PATH`:
   ```
   libtcmalloc_and_profiler.so.4 => /lib64/libtcmalloc_and_profiler.so.4 
(0x00007fa415ee3000)
   ```
   
   However, while I checked the libraries packed by 
[pack_server.sh](https://github.com/apache/incubator-pegasus/blob/master/scripts/pack_server.sh),
 I found `libtcmalloc_and_profiler.so`, rather than 
`libtcmalloc_and_profiler.so.4`. After I fixed 
[pack_server.sh](https://github.com/apache/incubator-pegasus/blob/master/scripts/pack_server.sh)
 to copy `libtcmalloc_and_profiler.so.4` into the package, the replica server 
did  not exit any more.


-- 
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: dev-unsubscr...@pegasus.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@pegasus.apache.org
For additional commands, e-mail: dev-h...@pegasus.apache.org

Reply via email to