WANG Cheng D
2014-Oct-28 01:33 UTC
[libvirt-users] Why a "core dump" error occurs when a thread exits in container but it's correct when running in native linux
Dear all, When I run my application in a container, sometimes the thread can exit correctly, sometime a "core dump" error occurs when it exits. But the application always exits correctly when it runs in a native fedora. Malloc() and free() functions are used in my application. I wonder if this is the reason for the core dump error. Is the thread exit event treated differently by the container and native OS? Or if I need to tune some options for memory in container's XML configuration file? Best wishes, Cheng
Apparently Analagous Threads
- [Bug 1652] New: rsync --timeout=n -> if timeout occurs, exits with no exitvalue
- Re: LXC + USB passthrough = Operation not permitted
- Re: LXC + USB passthrough = Operation not permitted
- Re: LXC + USB passthrough = Operation not permitted
- [Bug 1652] rsync --timeout=n -> if timeout occurs, exits with no exitvalue