HI All
I am doing first steps in debugging with GDB.
I have been suggested to redirect output to another terminal using the command using
I had a look at my ubuntu doing
and I cannot find this
.
What is it and how to achieve the same thing?
I am totally newbie so right now I doing some reading to understand how terminal works and what this command does. Do you have any suggestion or tip to follow that might help my research / improve my learning?
Hi,
In our HP-UX B.11.11. I could not find dev/urandom and dev/random
Are all pseudo-devices implemented as device drivers, or in need to run /configure some package to install the package to have dev/urandom.
Please help (4 Replies)
So, we removed a LUN from the SAN and the system is refusing to remove the references to it in the /dev folder. I've done the following:
devfsadm -Cv
powermt -q
luxadm -e offline <drive path>
luxadm probe
All those commands failed to remove the path. The drive stills shows up as <drive... (13 Replies)
I am not able to find menu.lst in /boot.
During the Linux Kernel Compilation I installed the kernel using make install.
Next I created an initrd image.
I had to modify the Grub configuration file - /boot/grub/menu.lst which I am not able to find.
Any resolution for the issue? (3 Replies)
Hello all.
I have a device thats suposed to be /dev/sg7 but when I do "ls -laF /dev/sg*" all sgXX are there from 0 to 15 except 7. what is going wrong:mad:. Please its urgent:wall: (1 Reply)
Our used size is 83 gb. Total of the folders and documents size is46,2 gb. 83-46=37 gb.
Where is my space. Where was lost?
Could you please I need your opinions?
{root}/space>du -s -h *
308K alaerrm-jprof
1K argerela
20G baerckup_in
1.8G cererm
28M ecerlipselink
... (8 Replies)
Hello,
I attached a tape drive to one of my partitions but i cannot find the device.
I run the command lsdev|grep rmt but i dont get anything in return.
When i run lsslot -c slot i can see the slot number and the device that belongs to the tape drive but i cannot find any rmt files in /dev.... (6 Replies)
Hi All
I would like to use the tool "pstack" to get a sample of the stack trace for a process.
As far as I understood It seems widely available in all Linux systems, but it is not in Ubuntu 10.10.
I tried using apt-get as per some posts in few forum, but it cannot be found in the APT... (9 Replies)
Hi, Anyone can help
My solaris 8 system has the following
/dev/null , /dev/tty and /dev/console
All permission are lrwxrwxrwx
Can this be change to a non-world write ??
any impact ?? (12 Replies)
Hello
I was doing a mksysb and was given an error message that my /dev/ipldevice was missing.
when i do an lslv -m hd5 i get the following output:
LP PP1 PV1 PP2 PV2 PP3 PV3
0001 0001 hdisk0
0002 0002 hdisk0
I check other... (3 Replies)
I am trying to run openwin on Solaris 5.8, but get an error:
/dev/fb: No such file or directory
Graphics Adapter device /dev/fb is of unknown type
Fatal server error:
InitOutput: Error loading module for /dev/fb
giving up.
/usr/openwin/bin/xinit: Connection refused (errno 146): ... (5 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)