10-20-2011
GDB No line in file error
Hi, I have a c program i compile with gcc4.5. This elf, if I use gdb and put a breakpoint on main, instead has a breakpoint in a function other than main or says no line in file.
I verified the elf is 1 to 1 with source, have all debug symbols for compilation etc.
The problem I think is the gdb version is older one on the target filesystem. Because If I use an older gcc to compile the program instead, gdb on target just works fine.
So the question is, are there any compile flags needed with gcc4.5 to support debugging on older gdb's?
10 More Discussions You Might Find Interesting
1. Programming
When I run gdb in solaris 8 for sparc, the error occurs like this:
“Segmentation Fault(core dumped)”
What's the problem?
Help! Thanks in advance! (2 Replies)
Discussion started by: new_hand
2 Replies
2. UNIX for Dummies Questions & Answers
Hi All,
I am unable to display the code in gdb. When i put list command i dont get any line. I mean i am unable to display the source line in gdb.
Can any body help me.
Thanks & Regards
Gauri (4 Replies)
Discussion started by: gauri
4 Replies
3. Programming
Hi people who have more of an idea about this than me,
For Uni we have to compile for the m68hc11. So I've set about setting up the toolchain so I can work at home as indicated here.
My problem is a make error when compiling GDB
make: *** No rule to make target `-lm', needed by `gdb'.... (1 Reply)
Discussion started by: madteckhead
1 Replies
4. Programming
If an executalbe file has several parameters, gdb can not pass parameters correctly. Let us see:
run:
./executablefile1 agr1 arg2 arg3
debug:
gdb executablefile1
run executalbefile1 arg1 arg2 arg3
then argv : executablefile1
argv : executablefile
argv : arg1
... (3 Replies)
Discussion started by: cdbug
3 Replies
5. Programming
I created one file (test.cpp)and complied it and get the executable file(test) and run it.It is giving the out put but when I am trying to debug that executable.I am getting the error --
please tell me the solutions??
Thanks in advance ..... (2 Replies)
Discussion started by: smartgupta
2 Replies
6. Programming
Consider the following program.
int main(){
struct a_t {
int *a;
unsigned char b;
unsigned char c;
unsigned char d;
} A;
unsigned char e;
unsigned char f;
unsigned char g;
g = 1;
A.a = (int *)&g; -> Memory misalignment... (1 Reply)
Discussion started by: balaji280283
1 Replies
7. Programming
Here is the program I am trying to debug:
#include <stdio.h>
int i = 5;
int main(void)
{
int x = 3;
display(x);
return 0;
}
void display(int x)
{
for ( i=0; i<x; ++i ) {
printf("i is %d.\n", i);
}
}This code is coming from here Peter's gdb Tutorial: Stepping... (2 Replies)
Discussion started by: ijustneeda
2 Replies
8. Programming
I'm sorry if the title is really criptic, but I don't know how to phrase my problem.
I know I can't really ask for a solution, and I normally wouldn't but this is really escaping my abilities.
Antefacts.
I developed a program using the zeromq messaging library.
I got to a point where the... (11 Replies)
Discussion started by: erupter
11 Replies
9. 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
10. UNIX for Dummies Questions & Answers
I have bunch of source code which I compiled using -ggdb3 flag.
I have copied the source code and executable to an another machine.
When I run the exe in gdb it does not show the statments at the line numbers when it breaks.
This is what I see
Breakpoint 1, TestCode (handler=0x806e110,... (1 Reply)
Discussion started by: rupeshkp728
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)