Sponsored Content
Top Forums UNIX for Dummies Questions & Answers How to write a new Gdb backend? Post 302753619 by Heeka on Wednesday 9th of January 2013 05:11:50 AM
Old 01-09-2013
How to write a new Gdb backend?

Hi Everyone,

I am new to Unix-like system and for GDB. I want to write a new GDB backend which will be possible either by GDB Generic or by GDB server or both. So does anyone has idea which one is preferable and from where and how should I start to write ? I sucessefully build gdb-7.5.50-1 in Cygwin environment.

Thanks in advance ..
Heeka
 

8 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

Kill a backend process

Hello, I am trying to kill a backend process i know i can type a simple command kill -9 pid and my process will be killed. But the task is that there are two commands in the script which run the backend process and when that script is runned then we cannot find the PID of the two commands ... (13 Replies)
Discussion started by: er_aparna
13 Replies

2. UNIX for Dummies Questions & Answers

Is it possible to combine MPI (as backend) and GTK (as frontend)

Hello All, i wonder if it make sense to attemp to use GTK to create a GUI as frontend handling data input and result display, and to use MPI to implement data process in the backend. I would be very grateful if you can provide an example code. Thanks, (0 Replies)
Discussion started by: cy163
0 Replies

3. AIX

Problem with custom print queue backend

I'm trying to write a custom backend (ksh script) for a print queue that will encrypt a file then FTP it to a server. I had been testing the script by just executing it by hand and giving it a file as an argument. When I run the script manually, everything works perfectly. But when I run the script... (0 Replies)
Discussion started by: acascianelli
0 Replies

4. IP Networking

read/write,write/write lock with smbclient fails

Hi, We have smb client running on two of the linux boxes and smb server on another linux system. During a backup operation which uses smb, read of a file was allowed while write to the same file was going on.Also simultaneous writes to the same file were allowed.Following are the settings in the... (1 Reply)
Discussion started by: swatidas11
1 Replies

5. Shell Programming and Scripting

Help with Informatica Backend Shell Script

Request Any one of your to provide me a script which does the following in a single unix script. Basically Users will load data in SHARED LINK everyday, should write a UNIX SCRIPT which will ........ 1) Unix script should Open the LINK (FTP) 2) Each DIRECTORY in the link contains many... (0 Replies)
Discussion started by: informaticalabs
0 Replies

6. Shell Programming and Scripting

Perl CGI. no output until backend script is done

It is a basic Perl CGI question, I want to print out "Processing ... " while backend script /script/wait.pl is still running. But acctually, nothing appeared in browser untill /script/wait.pl finished. print "Content-type:text/html\r\n\r\n"; print '<html>'; print '<head>'; print... (4 Replies)
Discussion started by: honglus
4 Replies

7. UNIX and Linux Applications

phonon-backend-gstreamer vs phonon-backend-vlc vs phonon-backend-xine

phonon-backend-gstreamer vs phonon-backend-vlc vs phonon-backend-xine What are the advantages and disadvantages of phonon-backend-gstreamer, phonon-backend-vlc, and phonon-backend-xine. I was reading this and got curious. ... (1 Reply)
Discussion started by: cokedude
1 Replies

8. Shell Programming and Scripting

Running backend processes in ssh

Hi Team, i have a script alloc.sh on server1 main () { if ; then (nohup ./alloc.sh ALLOCATE 5400 isogen_alloc_$2 < /dev/null 2> /dev/null &) echo ALLOC_OK exit 0 fi if ; then sleep $2 fi } main $@ Here if i execute the alloc.sh on server1, it gets executed... (1 Reply)
Discussion started by: chandana hs
1 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:15 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy