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)
I'm having problem understanding the how to use gdb command to debug my program. Can anyone give me some suggestion how to start, and examples. I read the manual in unix...I'm still confuse. (6 Replies)
Hi,
I'm trying to debug my gcc compiled code on my HPUX 11.23 (Itanium).
I searched the machine to find something that looks like a compiler, and what I found was :
adb (a bit unfriendly for debugging)
kwdb (I understand this is a kernel debugger)
gdb32
gdb64
gdbpa
When I run either... (0 Replies)
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)
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)
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)
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)
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 FREEBSD
gcore
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