Skip to content
Advertisement

Tag: debugging

Where the heck is that core dump?

TLDR: Can’t find the core dump even after setting ulimit and looking into apport. Sick of working so hard to get a single backtrace. Questions on the bottom. I’m having a little nightmare here. I’m currently doing some c coding, which in my case always means a metric ton of segfaults. Most of the times I’m able to reproduce the

could not to setup crash dump on centos7 for debug kernel

I am trying to setup kdump to generate the vmcore for kernel-3.10.0-123.el7. For the perf kernel kernel-3.10.0-123.el7.x86_64.rpm i setup kdump and kdump is working fine too, generating vmcore. Then i installed kernel-debug-3.10.0-123.el7.x86_64.rpm using yum install kernel-debug-3.10.0-123.el7.x86_64.rpm and kdump worked fine. But then i didnt have vmlinux to read vmcore of debug kernel. Then I build source using rpmbuild from the

debugging long running PHP script

I have php script running as a cron job, extensively using third party code. Script itself has a few thousands LOC. Basically it’s the data import / treatment script. (JSON to MySQL, but it also makes a lot of HTTP calls and some SOAP). Now, performance is downgrading with the time. When testing with a few records (around 100), performance

Debug information file conventions for Red Hat/Fedora?

According to lothar’s answer at How to generate gcc debug symbol outside the build target, I can create a two part executable – the stripped executable and the debug information file. After creating the stripped executable and the debug information file, I install the executable as normal (with make install). But I’m not sure what to do with the debug

visually debug GTK3 applications (GtkInspector / gtkparasite)

Trying to debug a GTK theme, I modified. Having corrected most of the issues with the theme, I Still cannot figure out, what color setting is responsible for background color in some input-fields or text-views. SETUP I can start GtkInspector as well as gtkparasite with Gtk3 applications (starting those debuggers as described on the given pages). I’m sure, the debugger

Good way to debug stack value corruption

What is a good way to debug stack value corruption. In a program of mine sometimes the address of the this pointer gets changed after a method returns that does a shutdown on a file descriptor. I debugged the program for hours but I can not find the problem. What is a good method to find out what changes the

debugging c using heap memory [closed]

Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers. This question does not appear to be about programming within the scope defined in the help center. Closed 9 years ago. Improve this question I am working with heap memory and I wrote an example below: I execute is as : ./heap test and the

Advertisement