05-20-2013
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 find the added code changes.
Through gdb command like info source and show dir. etc I see the code changes but breakpoints is not setting on that.
What might be the issue and how to get rid of this issue?
8 More Discussions You Might Find Interesting
1. Programming
I have to compile gnu-gdb 6.7 on HP-UX 11.11 with /usr/local/pa64/bin/gcc 64-bit compiler, but I'm having some problems during "make":
ser-tcp.c: In function `net_open':
ser-tcp.c:207: warning: passing arg 5 of `getsockopt' from incompatible pointer type
make: *** Error 1
make: Leaving... (8 Replies)
Discussion started by: untamed
8 Replies
2. Solaris
OS : SOLARIS 10
debug tool :$gdb -v
GNU gdb 6.6
compiler : $gcc -v
gcc version 2.95.3 20010315 (release)
When i tried to debug my application i got the following error.
$gdb Pal
GNU gdb 6.6
Copyright (C) 2006 Free Software Foundation, Inc.
This GDB was... (2 Replies)
Discussion started by: satish@123
2 Replies
3. Programming
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
4. Programming
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
5. Shell Programming and Scripting
Hi
i was going through the script debugging technique. below example was given in the book.
1 #!/bin/sh
2
3 Failed() {
4 if ; then
5 echo "Failed. Exiting." ; exit 1 ;
6 fi
7 echo "Done."
8 }
9
10 echo "Deleting old backups,... (11 Replies)
Discussion started by: scriptor
11 Replies
6. Red Hat
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
7. Programming
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... (4 Replies)
Discussion started by: biju64
4 Replies
8. Programming
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
GZEXE(1) General Commands Manual GZEXE(1)
NAME
gzexe - compress executable files in place
SYNOPSIS
gzexe name ...
DESCRIPTION
The gzexe utility allows you to compress executables in place and have them automatically uncompress and execute when you run them (at a
penalty in performance). For example if you execute ``gzexe /usr/bin/gdb'' it will create the following two files:
-rwxr-xr-x 1 root root 1026675 Jun 7 13:53 /usr/bin/gdb
-rwxr-xr-x 1 root root 2304524 May 30 13:02 /usr/bin/gdb~
/usr/bin/gdb~ is the original file and /usr/bin/gdb is the self-uncompressing executable file. You can remove /usr/bin/gdb~ once you are
sure that /usr/bin/gdb works properly.
This utility is most useful on systems with very small disks.
OPTIONS
-d Decompress the given executables instead of compressing them.
SEE ALSO
gzip(1), znew(1), zmore(1), zcmp(1), zforce(1)
CAVEATS
The compressed executable is a shell script. This may create some security holes. In particular, the compressed executable relies on the
PATH environment variable to find gzip and some standard utilities (basename, chmod, ln, mkdir, mktemp, rm, sleep, and tail).
BUGS
gzexe attempts to retain the original file attributes on the compressed executable, but you may have to fix them manually in some cases,
using chmod or chown.
GZEXE(1)