04-10-2013
Did you compile it with the debugging "-g" switch on...
10 More Discussions You Might Find Interesting
1. Programming
Which is better??
I have always been a gdb fan.. But ppl say dbx is beter better for debugging the core.. Do all GDB lovers agree to it???
:cool: (1 Reply)
Discussion started by: jyotipg
1 Replies
2. Programming
Can anyone give me the link to a website having gdb tutorials
(for advanaced debugging & shortcuts)
http://www.burneddowndays.com/talk/YaBBImages/rolleyes.gif (1 Reply)
Discussion started by: wojtyla
1 Replies
3. Solaris
I want to install gdb on SunOS 5.6 machine. Where can i download from ? (1 Reply)
Discussion started by: shafi2all
1 Replies
4. UNIX for Advanced & Expert Users
Hi,
This is a simple question on GDB. Given a core file, how can you check which process has dumped the core?
Regards
- Krishna (1 Reply)
Discussion started by: krishnamurthig
1 Replies
5. UNIX for Advanced & Expert Users
Hi All,
I wanted to know if there is a core file generated and I am not sure for which Binary it is generated .
Can I use gdb to debug the core file ?
Thanks. (1 Reply)
Discussion started by: shubhranshu
1 Replies
6. UNIX for Advanced & Expert Users
Hi All,
I am trying to execute a binary and it is giving Segmentation Fault.
Can I use gdb to debug this error?
Secondly there is no core file generated , so when I an trying to run gdb with the binary only I am not able to set any breakpoints.
When I am running the gdb and the I am... (1 Reply)
Discussion started by: shubhranshu
1 Replies
7. Programming
Hello,
I am having problem with debugging my code. I am writing a C code and then I compile it with the Makefile. I make a target file and then copy it in my Robot(Khepera III) and then run the program over there.
I compile it ofcorse on my machine and then copy the compiled file in the... (10 Replies)
Discussion started by: mind@work
10 Replies
8. Programming
i have created some break points in gdb.
let's say....
b sqlcxt
how can i know the breakpoint name of sqlcxt ??? (1 Reply)
Discussion started by: lipun4u
1 Replies
9. Programming
Hi, I got:
host machine: RedHat (RHEL6)
virtual machine: RedHat (RHEL6)
I run (on host machine):
qemu-system-x86_64 ...... -S -s
after that i run (on host machine):
gdb
target remote localhost:1234
set architecture i386:x86-64
and then i can use (on host machine) 'ctrl + c' to... (2 Replies)
Discussion started by: Chrisdot
2 Replies
10. Programming
Hi, all
I try to understand the output from gdb
Program received signal SIGABRT, Aborted.
*** glibc detected *** /home/sys_cbo/dev/zif/bin/Debug/zifd: free(): invalid pointer: 0x00007fffac04d3d0 ***
how should i read this?
(gdb) backtrace
#0 0x0000003015e32925 in raise () from... (1 Reply)
Discussion started by: huvcbo
1 Replies
LEARN ABOUT SUSE
ipc::run::debug
IPC::Run::Debug(3) User Contributed Perl Documentation IPC::Run::Debug(3)
NAME
IPC::Run::Debug - debugging routines for IPC::Run
SYNOPSIS
##
## Environment variable usage
##
## To force debugging off and shave a bit of CPU and memory
## by compile-time optimizing away all debugging code in IPC::Run
## (debug => ...) options to IPC::Run will be ignored.
export IPCRUNDEBUG=none
## To force debugging on (levels are from 0..10)
export IPCRUNDEBUG=basic
## Leave unset or set to "" to compile in debugging support and
## allow runtime control of it using the debug option.
DESCRIPTION
Controls IPC::Run debugging. Debugging levels are now set by using words, but the numbers shown are still supported for backwards
compatibility:
0 none disabled (special, see below)
1 basic what's running
2 data what's being sent/recieved
3 details what's going on in more detail
4 gory way too much detail for most uses
10 all use this when submitting bug reports
noopts optimizations forbidden due to inherited STDIN
The "none" level is special when the environment variable IPCRUNDEBUG is set to this the first time IPC::Run::Debug is loaded: it prevents
the debugging code from being compiled in to the remaining IPC::Run modules, saving a bit of cpu.
To do this in a script, here's a way that allows it to be overridden:
BEGIN {
unless ( defined $ENV{IPCRUNDEBUG} ) {
eval 'local $ENV{IPCRUNDEBUG} = "none"; require IPC::Run::Debug"'
or die $@;
}
}
This should force IPC::Run to not be debuggable unless somebody sets the IPCRUNDEBUG flag; modify this formula to grep @ARGV if need be:
BEGIN {
unless ( grep /^--debug/, @ARGV ) {
eval 'local $ENV{IPCRUNDEBUG} = "none"; require IPC::Run::Debug"'
or die $@;
}
Both of those are untested.
AUTHOR
Barrie Slaymaker <barries@slaysys.com>, with numerous suggestions by p5p.
perl v5.12.1 2010-04-01 IPC::Run::Debug(3)