coredump

How do I detect what application generated a specific core dump on OS X?

由 China☆狼群 提交于 2019-12-08 13:20:22
问题 I want to detect what application generated a core dump on OS X. How can I find this information? Runing file core.1234 does not give the application name, online something like Mach-O 64-bit core x86_64 . 回答1: You use otool : $ otool -c core.1234 for more, see man page. More magics can be found in this fantastic document Mac OS X debugging magic. 来源： https://stackoverflow.com/questions/3779625/how-do-i-detect-what-application-generated-a-specific-core-dump-on-os-x

core dumped in C programming

由 守給你的承諾、 提交于 2019-12-08 13:16:49
问题 I have a homework that's supposed to ask the user for a number and make a square with the length being the number they put. If the user types in 5, then the program needs to make a square that is 5x5. When I compile it, i get a segmentation fault (core dumped). I have no idea where the problem is. Can you guys help me? I even tried running the program with paper and pencil to see what my output would be and it seemed fine to me. #include <stdio.h> int main (){ int size, limit = 0; char ch =

Passing Object over Server to client

由 邮差的信 提交于 2019-12-08 10:28:45
问题 I am trying to create a client server application in linux. Server is supposed to send one object to all connected clients. Here is the code for it. In this When server send object, everything remains ok at server side but Segmentation fault occurs on client server immediately it receive it. Server: #include "Question.h" #include <iostream> #include <string.h> using namespace std; #include<sys/socket.h> #include<sys/types.h> #include<stdio.h> #include<arpa/inet.h> #include<time.h> #include

Is it possible to get a Linux coredump that only contains callstack, threads, and local variables?

由 故事扮演 提交于 2019-12-08 04:18:03
问题 My company is utilizing the coredump functionality in Linux (CentOS specifically) to track down some hard to find issues. Unfortunately, we have a bunch of small VMs running with limited HD space and the full core dumps are causing issues because of the large amount of space taken up by the heaps. Is it possible to just have Linux dump the callstack, threads and local variables when a segmentation fault occurs? I tried just limiting the dumps to 50 megs, but it doesn't seem like all the

Windows Crash Dump call stack only shows wow64

由 喜欢而已 提交于 2019-12-07 06:49:37
问题 Problem I have a Windows application that we developed for in house use. Thanks to Windows Error Handling, the window stays open and I can easily generate a crash dump from the task manager. I have used crash-dumps on linux through eclipse once before, but this is the first time on Windows. Hardware The server is Windows 2012, and my development machine is Windows 7. Windbg When I load the crash dump in Windbg, load my symbols, then choose to look at the call stack, the only listings are: How

Is it possible to get a Linux coredump that only contains callstack, threads, and local variables?

由 邮差的信 提交于 2019-12-07 01:04:33
My company is utilizing the coredump functionality in Linux (CentOS specifically) to track down some hard to find issues. Unfortunately, we have a bunch of small VMs running with limited HD space and the full core dumps are causing issues because of the large amount of space taken up by the heaps. Is it possible to just have Linux dump the callstack, threads and local variables when a segmentation fault occurs? I tried just limiting the dumps to 50 megs, but it doesn't seem like all the desired details are in that first 50 megabytes (ulimit -c 51200). We're okay truncating the heap like that,

Is it possible to debug core file generated by a executable compiled without gdb flag?

由 余生颓废 提交于 2019-12-06 22:43:01
问题 Is it possible to debug core file generated by a executable compiled without gdb flag ? If yes, any pointers or tutorials on it ? 回答1: Yes you can. It will not be easy though. I will give you an example. Lets say that I have the following program called foo.c : main() { *((char *) 0) = '\0'; } I'll compile it and make sure that there is no symbols: $ cc foo.c $ strip a.out $ file a.out a.out: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), dynamically linked (uses shared libs), for

Linux core dumps are too large!

由 天大地大妈咪最大 提交于 2019-12-06 22:19:03
问题 Recently I've been noticing an increase in the size of the core dumps generated by my application. Initially, they were just around 5MB in size and contained around 5 stack frames, and now I have core dumps of > 2GBs and the information contained within them are no different from the smaller dumps. Is there any way I can control the size of core dumps generated? Shouldn't they be at least smaller than the application binary itself? Binaries are compiled in this way: Compiled in release mode

infinite abort() in a backrace of a c++ program core dump

由 微笑、不失礼 提交于 2019-12-06 20:04:23
问题 I have a strange problem that I can't solve. Please help! The program is a multithreaded c++ application that runs on ARM Linux machine. Recently I began testing it for the long runs and sometimes it crashes after 1-2 days like so: *** glibc detected ** /root/client/my_program: free(): invalid pointer: 0x002a9408 *** When I open core dump I see that the main thread it seems has a corrupt stack: all I can see is infinite abort() calls. GNU gdb (GDB) 7.3 ... This GDB was configured as "--host

Accessing random image pixels using a for loop

由 天涯浪子 提交于 2019-12-06 12:48:42
I am trying to learn image processing using OpenCV . I wrote some code to edit an image. The edits are working well except for changing the color of some pixels. I am trying to access some random pixels, and change their color (that is when status == 3 ). When I run the program I get "[run] Segmentation fault (core dumped)" , which I think means that there is a denied memory access. int main( ) { Mat originalImage = imread("image.jpg", CV_LOAD_IMAGE_UNCHANGED); if (originalImage.empty()){ cout << "Error : Image cannot be loaded..!!" << endl; return -1; } int orgRows = originalImage.rows; int
订阅 coredump