Gdb error while debugging core file Post: 302891737

9 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

Using GDB to analyse different CORE dumps

Hi, Can we modify the GDB source code so as to analyze core dumps from different targets? From my analysis, I think we need to build our section table statically for each target. i.e., including the various address boundaries in build_section_table() function. If this is the case, then the GDB...

2. Programming

Debugging 64bit code with gdb and ddd in AIX

I'm trying to use the GDB debugger and DDD to debug 64bit code. It seems that the AIX toolkit gdb version 6.0 works with 64bit code. But the ddd tool when running gdb gives the following errors : Starting program: <my binary> <my params> warning: "": not in executable format: There is an input...

3. UNIX for Dummies Questions & Answers

Debugging core file from another server

Hi all, One fine day one of the services in our prod server started core dumping and then the core file was ftp'd to our test server , to debug we used gdb with the executable which we had but we could not get the function names ( maybe due to missing symbols ) How do i solve this ...

4. Programming

Debugging a running process in GDB

Hi , Any gdb user could see my problem. Let me describe what i want to do. i have a test utility to send message to running process. My interest is to go through to functions calls when my test case starts. In a simple way i want have a code walk for a particular scenario of a test...

5. Linux

unable to read core dumps on unix. Is there another way than using GDB?

hi all, I am having set of core dumps obtained from client server. Now i am trying to read them but unable to do so. I have few queries: 1. Core dumps were generated on some xyz server and copied to my unix virtual. Can I read them as text here? 2. I tried installing gdb-7.3 but when i fire...

6. UNIX for Dummies Questions & Answers

GDB Debugging Problem

I have added some code in my file. I have created executable rpm file of our code and also I have created debuginfo and debugsource files and installed all three. But when I debug in gdb I see the the code changes in soucre file. But the break point does not hit at that place as if it did not...

7. Programming

64 bit code debugging using gdb and ddd

Hello I have built our application on AIX 7.1 as a 64 bit application. My queries are as follows: Can a 32bit gdb (v7.6) and ddd (data display debugger - v3.3.12), debug a 64bit executable ? If I have a small 64bit a.exe executable that seems to work. If I have a more complicated executable...

8. Programming

Best guide or video for gdb <register level debugging>

would like to know best guide or document for gdb for different architectures x86 , power pc etc.. would like to understand how to debug segmentation faults because of stack corruption .. understand utilities ELF , objdump etc.. please guide me

9. Programming

Best reference for understanding core file and debugging for different architectures

Hi , could someone suggest best reference for core file understanding , analysis , debugging for different architectures like what registers represent what in a architecture specific core .. how to get maximum information out of corrupted core different tools and how they work and how to...

LEARN ABOUT CENTOS

abrtd

ABRTD(8)							    ABRT Manual 							  ABRTD(8)

NAME

       abrtd - automated bug reporting tool's daemon.

SYNOPSIS

       abrtd [-dsv[v]...]

DESCRIPTION

       abrtd is a daemon that watches for application crashes. When a crash occurs, it collects the problem data (core file, application's command
       line etc.) and takes action according to the type of application that crashed and according to the configuration in the abrt.conf config
       file. There are plugins for various actions: for example to report the crash to Bugzilla, to mail the report, or to transfer the report via
       FTP or SCP. See the manual pages for the respective plugins.

OPTIONS

       -v
	   Log more detailed debugging information.

       -d
	   Stay in the foreground and log to standard error.

       -s
	   Log to system log even with option -d.

       -t NUM
	   Exit after NUM seconds of inactivity.

       -p
	   Add program names to log.

CAVEATS

       When you use some other crash-catching tool specific for an application or an application type (for example BugBuddy for GNOME
       applications), crashes of this type will be handled by that tool and not by abrtd. If you want abrtd to handle these crashes, turn off the
       higher-level crash-catching tool.

AUTHORS

       o   ABRT team

SEE ALSO

       abrt.conf(5)

abrt 2.1.11							    06/18/2014								  ABRTD(8)