10 More Discussions You Might Find Interesting
1. Programming
Are the following equivalent?
static int df, dl, du, count;
static int df;
static int dl;
static int du;
static int count; (7 Replies)
Discussion started by: kristinu
7 Replies
2. Shell Programming and Scripting
I have the below code to find yesterdays date, In this I want to make MONTH, DAY and YEAR as global variableand use it outside the {}, but I am unable to do so , please assist:
#!/usr/bin/ksh
date '+%m %d %Y' |
{
read MONTH DAY YEAR
DAY=`expr "$DAY" - $1`
case "$DAY" in
0) ... (1 Reply)
Discussion started by: mohsin.quazi
1 Replies
3. Shell Programming and Scripting
program name--test
#!/bin/bash
output1=`/home/user/a.c`
output2=`/home/user/a.c`
k=`$output1 + 1`
m=`$output2 + 1`
echo $k
echo $m
---------------------------------------------------------------------------
prgram name--a.c
#include<stdio.h>
int main() (1 Reply)
Discussion started by: sameworld1980
1 Replies
4. Shell Programming and Scripting
Hi,
I have a shell script wherein i am doing some file operations and storing the data in some variables. I am exporting these variables as i need to use them outside shell. Then within the shell i am launching GDB session hoping that i will be able to access the exported variables in the GDB... (2 Replies)
Discussion started by: jsantosh
2 Replies
5. Programming
Hi,
consider the following script.
ip='***.***.**.**'
user='****'
pw='******'
ftpresults=`ftp -nv $ip<<EOF
user $user $pw
cd /home/oracle/practice
size $1
bye
EOF`
fname=$1
echo $ftpresults
sqlplus -s tms/tms@dev45 <<"EOF"
insert into remote_file_sizes (file_name,file_size)... (1 Reply)
Discussion started by: ravi raj kumar
1 Replies
6. Shell Programming and Scripting
I can't figure out how to access variables that are stored in a separate file. Can someone let me in on the secret? Please, and thank you.
-Kevin (7 Replies)
Discussion started by: wayne1411
7 Replies
7. HP-UX
Hi,
I don't know if this is HP-UX specific, but I'll take my chances with this forum. ;)
I'm using WDB 5.7 on HP Itanium 11.23.
'file' on my executable shows:
ELF-32 executable object file - IA64
The problem is with viewing the contents of the variables.
Following is a sequence that... (0 Replies)
Discussion started by: rimon
0 Replies
8. Shell Programming and Scripting
hi everybody!
i am running this ksh script for replacing a set of strings by another set of new ones. i am getting both these from a file.
also, the strings that i want to replace, are sub-strings(can occur more than once in each chunk) in a big chunk of data that i have bulk-copied(bcp utility)... (1 Reply)
Discussion started by: trupti wagh
1 Replies
9. Shell Programming and Scripting
Hi all,
I have a perl script which declares two variables and calls another perl script which accesses those variables. But I am unable to access the variables in the called script. My script is as follows:
my $ENV{a}="20";
system("perl called.pl");
and my called.pl contains:
print... (3 Replies)
Discussion started by: gurukottur
3 Replies
10. Programming
Hi
I want to know when and where memory for static variables are allocated in a C program. If it allocates during compilation will memory be allocated for the variable "i" during compilation itself.
int count();
int main(){
printf("%d", count());
return 0;
}
int count()
{
... (8 Replies)
Discussion started by: nathanmca
8 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)