coredump

问题 Is there a way to figure out if a method ever been called inside running JVM. Let's say I have the following method information and I want to know if it has ever been called: "methodId": { "className": "InvokerParser", "filePath": "org/foo/commons/functors/InvokerParserformer.java", "methodName": "parser" } 回答1: If the application is running on HotSpot JVM, it is possible to get the information about the given method using HotSpot Serviceability Agent. Here is a tool that checks whether the

问题 Is there a way to figure out if a method ever been called inside running JVM. Let's say I have the following method information and I want to know if it has ever been called: "methodId": { "className": "InvokerParser", "filePath": "org/foo/commons/functors/InvokerParserformer.java", "methodName": "parser" } 回答1: If the application is running on HotSpot JVM, it is possible to get the information about the given method using HotSpot Serviceability Agent. Here is a tool that checks whether the

问题 I want to avoid dumping certain information from my program into a core file in case of any crash. For that, I can use coredump_filter (http://man7.org/linux/man-pages/man5/core.5.html) The man page provides following description The value in the file is a bit mask of memory mapping types (see mmap(2)). If a bit is set in the mask, then memory mappings of the corresponding type are dumped; otherwise they are not dumped. The bits in this file have the following meanings: bit 0 Dump anonymous

问题 This question already has an answer here : How to find which thread caused SEGFAULT in a post-mortem gdb session? (1 answer) Closed 6 years ago . My application uses more than 8 threads. When I run info threads in gdb I see the threads and the last function they were executing. It does not seem obvious to me exactly which thread caused the SIGSEGV. Is it possible to tell it? Is it thread 1? How are the threads numbered? 回答1: When you use gdb to analyze the core dump file, the gdb will stop at

问题 This question already has an answer here : How to find which thread caused SEGFAULT in a post-mortem gdb session? (1 answer) Closed 6 years ago . My application uses more than 8 threads. When I run info threads in gdb I see the threads and the last function they were executing. It does not seem obvious to me exactly which thread caused the SIGSEGV. Is it possible to tell it? Is it thread 1? How are the threads numbered? 回答1: When you use gdb to analyze the core dump file, the gdb will stop at

问题 I have a C++ application (for OS X) that calls lua as a scripting language. I'm running a large number of these applications (100s) and they can run for a very long time (days or weeks). Sometimes one crashes. And when it crashes it leaves me a lovely core file. I can open this core file in gdb and find where the application crashes. I can walk the call stack and find an instance of a lua_State variable. My problem is that I'd like to see what the lua call stack looks like at this time...

问题 I have a C++ application (for OS X) that calls lua as a scripting language. I'm running a large number of these applications (100s) and they can run for a very long time (days or weeks). Sometimes one crashes. And when it crashes it leaves me a lovely core file. I can open this core file in gdb and find where the application crashes. I can walk the call stack and find an instance of a lua_State variable. My problem is that I'd like to see what the lua call stack looks like at this time...

来源： https://stackoverflow.com/questions/63371514/how-to-install-php-debug-symbols-on-debian-buster

问题 using ulimit command, i set core file size. ulimit -c unlimited and I compiled c source code using gcc - g option. then a.out generated. after command ./a.out there is runtime error . (core dumped) but core file was not generated.(ex. core.294340) how to generated core file? 回答1: First make sure the container will write the cores to an existing location in the container filesystem. The core generation settings are set in the host, not in the container. Example: echo '/cores/core.%e.%p' | sudo

问题 My PHP container runs puppeteer to generate PDF. By generating a PDF document, it also creates two core dump files inside my container. I am not sure where they actually come from. The host/server is CentOS 7. I've checked following: No application error log, Browsershot/puppeteer is running without errors. No error log (e.g. segfault) found in /var/log/messages I've tried to disable core dumps By following Disable core dumps section of https://linux-audit.com/understand-and-configure-core