Sponsored Content
Top Forums Programming 64 bit code debugging using gdb and ddd Post 302892009 by biju64 on Monday 10th of March 2014 09:24:33 AM
Old 03-10-2014
Thanks for the quick reply Pravin_218.
So I guess I'll have to rebuild both gdb & ddd in 64 bit mode.
Finding it hard to build gdb in 64bit as the code does not seem to be geared towards a 64bit build. Getting errors such as:

aix5ppc-core.c: In function 'xcoff64_core_p':
aix5ppc-core.c:194:13: error: assignment makes integer from pointer without a cast [-Werror]
sec->vma = ldinfo.ldinfo_dataorg;

If anyone has any idea on what to do about such errors please help.
 

9 More Discussions You Might Find Interesting

1. 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... (2 Replies)
Discussion started by: bean66
2 Replies

2. 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... (1 Reply)
Discussion started by: meet123321
1 Replies

3. Programming

ddd/gdb debugger problem

I hope this is the right thread - not sure if it belongs in the Linux forum. Anyway, I'm having an issue with ddd and gdb. When using ddd to run gdb, there are extra parameters being appended, and my program is picking them up. I'm running on Ubuntu 11.04... Here's my command line entry - ... (1 Reply)
Discussion started by: jalburger
1 Replies

4. UNIX for Advanced & Expert Users

DDD and GDB rereads ~/.cshrc

Who know why GDB reads my ~/.cshrc again when I type "run" command? Same happends when run DDD debugger (it runs GDB inside) I need the program to inherit the environment from the current shell. How to disable this behavior? I use GNU gdb (GDB) Red Hat Enterprise Linux (7.0.1-32.el5_6.2) (3 Replies)
Discussion started by: baruchgu
3 Replies

5. UNIX for Dummies Questions & Answers

DDD is waiting for GDB to get Ready

Hello, I'm attempting to use the DDD program. After launching it from the shell I try to set a breakpoint on a source code file and when I click run it hangs and says Waiting until GDB gets ready. I cannot do anything inside the program except quit (and even that takes a while). Can someone tell... (3 Replies)
Discussion started by: lamentofking
3 Replies

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... (1 Reply)
Discussion started by: rupeshkp728
1 Replies

7. Red Hat

Gdb error while debugging core file

Hi, I am trying to analyze one core file on my RHEL 6.5, but I am getting below error related to the core file. So I am not getting any stack trace about the crash. # gdb MyDebugBin /var/core/MyDebugBin.27005 GNU gdb (GDB) Red Hat Enterprise Linux (7.2-60.el6_4.1) Copyright (C) 2010 Free... (2 Replies)
Discussion started by: sanzee007
2 Replies

8. AIX

Gdb on a 64 bit executable - cannot access memory

Hi, Can anyone explain this please..... A simple test program... ### snip #include <stdio.h> main() { static int n; n = 6; printf("hello %d\n", n); n=7; } ### snip 64 bit compile/link.... (2 Replies)
Discussion started by: bagpussnz
2 Replies

9. 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 (1 Reply)
Discussion started by: Gopi Krishna P
1 Replies
GCORE(1)						    BSD General Commands Manual 						  GCORE(1)

NAME
gcore -- get core images of running process SYNOPSIS
gcore [-f] [-s] [-c core] [executable] pid DESCRIPTION
The gcore utility creates a core image of the specified process, suitable for use with gdb(1). By default, the core is written to the file ``core.<pid>''. The process identifier, pid, must be given on the command line. The following options are available: -c Write the core file to the specified file instead of ``core.<pid>''. -f Dumps all available segments, excluding only malformed and undumpable segments. Unlike the default invocation, this flag dumps map- pings of devices which may invalidate the state of device transactions or trigger other unexpected behavior. As a result, this flag should only be used when the behavior of the application and any devices it has mapped is fully understood and any side effects can be controlled or tolerated. -s Stop the process while gathering the core image, and resume it when done. This guarantees that the resulting core dump will be in a consistent state. The process is resumed even if it was already stopped. The same effect can be achieved manually with kill(1). FILES
core.<pid> the core image HISTORY
A gcore utility appeared in 4.2BSD. BUGS
Because of the ptrace(2) usage gcore may not work with processes which are actively being investigated with truss(1) or gdb(1). Addition- ally, interruptable sleeps may exit with EINTR. The gcore utility is not compatible with the original 4.2BSD version. BSD
July 14, 2010 BSD
All times are GMT -4. The time now is 09:27 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy