Sponsored Content
Full Discussion: GDB or DBX??
Top Forums Programming GDB or DBX?? Post 39900 by Synbios on Wednesday 3rd of September 2003 06:49:48 PM
Old 09-03-2003
I like GDB. But don't forget there is also DDD.
 

10 More Discussions You Might Find Interesting

1. Solaris

Help required on DBX

Hi All, I've been using Linux for past 2yrs for professional dev. Im well-off with gnu gdb. I am a C++ developer. Now that i use solaris, I need help on DBX. Regards, Sumanth (1 Reply)
Discussion started by: Sumanth
1 Replies

2. Programming

clearing breakpoints using dbx v 7.2.1

Im unsure of how to clear break points using dbx v7.2.1 Ive tried using delete linenumber of breakpoint however this does not seem to work. Could anyone point me in the correct direction ? regards (0 Replies)
Discussion started by: JamesGoh
0 Replies

3. Programming

No dbx installed

I have a problem whith dbx: there is no dbx installed!!! Could someone tell me where do i get dbx program and how to install it? Thanks. (1 Reply)
Discussion started by: calloc
1 Replies

4. UNIX for Advanced & Expert Users

need help on dbx commands?

Hi .. I have a core_dump in the server... AIX 5.3 . It was created by on proc executable called "ProcessIse" . from the log report i found the source file name "ProcessIseInterface.C" which created the core file. the core file name is : "core" under /iprs/bin directory. can you help me... (1 Reply)
Discussion started by: vparunkumar
1 Replies

5. AIX

dbx fatal error

Background ------------- Os: IBM AIXL 5.1 (Unix) Problem ------------- I run the dbx in csh as follows % dbx mainprog -- The following is the systemm replay Type 'help' for help. reading symbolic information ...warning: stab entry unrecognized: name ,type 45, class a8, value 0' ... (1 Reply)
Discussion started by: skfn1203
1 Replies

6. Programming

dbx issue

hi i have executable(eg test) of my application that has the following syntax to run test -Ddatabase_name Inputfile Now i want to debug it using dbx so i do dbx test (dbx) stop at /abc/test/test.c:90 stop at /abc/test/test.c:90 ^ syntax error the... (0 Replies)
Discussion started by: mad_man12
0 Replies

7. AIX

Using dbx on AIX

Hi, We are porting a virtual machine application which emits native PowerPC instructions. The instructions are written to the data segment and are then executed, similar to the JIT / hot spot technology used in the Java VM. The problem is that the AIX debugger (dbx) will not show me stack... (3 Replies)
Discussion started by: nrgiii
3 Replies

8. Shell Programming and Scripting

How to use dbx on AIX?

Hi, I ahd created my executable file from makefile on AIX. Now I want to debug my code using dbx. I typed: dbx help It goes into (dbx) prompt But afte that i do not know what to do to put breakpoints in my program and how to run step by step. Help me out ASAP. Thanks in... (0 Replies)
Discussion started by: Poonamol
0 Replies

9. Programming

Dbx Debugger

I have tried lots of stuff but i can't get it working, i have also found a Thread in this Forum about it but it didn't describe how the program has to be run ect. My issue is that i want to run a program with multiple arguments eg. ./myprog arg1 arg2 arg3 arg4 arg5 with dbx, but i cant get... (8 Replies)
Discussion started by: alcatros
8 Replies

10. UNIX for Dummies Questions & Answers

Problems with the dbx debugger

hey everyone, i'm having a little problem with my dbx debugger. the problem is that when i try to print a struct it print it as a struct from another type. i even tried casting the struct to its type and it still print it as the other type.. anyone had that problem and solved it? or maybe have... (4 Replies)
Discussion started by: sabres207
4 Replies
gdbserver(1)						       GNU Development Tools						      gdbserver(1)

NAME
gdbserver - Remote Server for the GNU Debugger SYNOPSIS
gdbserver tty prog [args...] gdbserver tty --attach PID DESCRIPTION
GDBSERVER is a program that allows you to run GDB on a different machine than the one which is running the program being debugged. Usage (server (target) side): First, you need to have a copy of the program you want to debug put onto the target system. The program can be stripped to save space if needed, as GDBserver doesn't care about symbols. All symbol handling is taken care of by the GDB running on the host system. To use the server, you log on to the target system, and run the `gdbserver' program. You must tell it (a) how to communicate with GDB, (b) the name of your program, and (c) its arguments. The general syntax is: target> gdbserver COMM PROGRAM [ARGS ...] For example, using a serial port, you might say: target> gdbserver /dev/com1 emacs foo.txt This tells gdbserver to debug emacs with an argument of foo.txt, and to communicate with GDB via /dev/com1. Gdbserver now waits patiently for the host GDB to communicate with it. To use a TCP connection, you could say: target> gdbserver host:2345 emacs foo.txt This says pretty much the same thing as the last example, except that we are going to communicate with the host GDB via TCP. The `host:2345' argument means that we are expecting to see a TCP connection from `host' to local TCP port 2345. (Currently, the `host' part is ignored.) You can choose any number you want for the port number as long as it does not conflict with any existing TCP ports on the target system. This same port number must be used in the host GDBs `target remote' command, which will be described shortly. Note that if you chose a port number that conflicts with another service, gdbserver will print an error message and exit. On some targets, gdbserver can also attach to running programs. This is accomplished via the --attach argument. The syntax is: target> gdbserver COMM --attach PID PID is the process ID of a currently running process. It isn't necessary to point gdbserver at a binary for the running process. Usage (host side): You need an unstripped copy of the target program on your host system, since GDB needs to examine it's symbol tables and such. Start up GDB as you normally would, with the target program as the first argument. (You may need to use the --baud option if the serial line is running at anything except 9600 baud.) Ie: `gdb TARGET-PROG', or `gdb --baud BAUD TARGET-PROG'. After that, the only new command you need to know about is `target remote'. It's argument is either a device name (usually a serial device, like `/dev/ttyb'), or a HOST:PORT descriptor. For example: (gdb) target remote /dev/ttyb communicates with the server via serial line /dev/ttyb, and: (gdb) target remote the-target:2345 communicates via a TCP connection to port 2345 on host `the-target', where you previously started up gdbserver with the same port number. Note that for TCP connections, you must start up gdbserver prior to using the `target remote' command, otherwise you may get an error that looks something like `Connection refused'. OPTIONS
You have to supply the name of the program to debug and the tty to communicate on; the remote GDB will do everything else. Any remaining arguments will be passed to the program verbatim. SEE ALSO
`gdb' entry in info; Using GDB: A Guide to the GNU Source-Level Debugger, Richard M. Stallman and Roland H. Pesch, July 1991. COPYING
Copyright (c) 1993 Free Software Foundation, Inc. Permission is granted to make and distribute verbatim copies of this manual provided the copyright notice and this permission notice are preserved on all copies. Permission is granted to copy and distribute modified versions of this manual under the conditions for verbatim copying, provided that the entire resulting derived work is distributed under the terms of a permission notice identical to this one. Permission is granted to copy and distribute translations of this manual into another language, under the above conditions for modified versions, except that this permission notice may be included in translations approved by the Free Software Foundation instead of in the original English. Cygnus Support 2 November 1993 gdbserver(1)
All times are GMT -4. The time now is 02:42 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy