|
|
Sponsored Content
Top Forums
Programming
GDB No line in file error
Post 302566722 by atulmt on Friday 21st of October 2011 02:37:16 AM
10-21-2011
Hi,
i am not able to see the listing of code in the gdb. i tried to use the directory command to give the soure directory tree but it is not working
any suggestion
i am not able to see the listing of code in the gdb. i tried to use the directory command to give the soure directory tree but it is not working
any suggestion|
|
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
LEARN ABOUT FREEBSD
elf_end
ELF_END(3) BSD Library Functions Manual ELF_END(3) NAME
elf_end -- release an ELF descriptor LIBRARY
ELF Access Library (libelf, -lelf) SYNOPSIS
#include <libelf.h> int elf_end(Elf *elf); DESCRIPTION
Function elf_end() is used to release the resources associated with an ELF descriptor pointed to by argument elf. This descriptor must have been allocated by a previous call to elf_begin(3) or elf_memory(3). For programming convenience, a NULL value is permitted for argument elf. A call to elf_end() decrements the activation count for descriptor elf by one. The resources associated with the descriptor are only released with its activation count goes to zero. Once function elf_end() returns zero, the ELF descriptor elf will no longer be valid and should not be used further. RETURN VALUES
Function elf_end() returns the current value of the ELF descriptor elf's activation count, or zero if argument elf was NULL. SEE ALSO
elf(3), elf_begin(3), elf_memory(3), gelf(3) BSD
June 29, 2006 BSD