07-16-2011
basically i run "gdbserver remote:80 ./test" on an i386 target platform. On host i do gdb test. Then on gdb prompt--
target remote <targetIP:80>
break main
cont
it breaks at main, when i do next to single step i get
0x08048810 in printf@plt ()
9 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
Hi,
If we want to debug a shell script, then set -vx has to be included in the begining of the script. Just i want to know what purpose -vx is used.
Thanks in advace
Sarwan (2 Replies)
Discussion started by: sarwan
2 Replies
2. Programming
I'm running one multithreaded application, in that one of my thread
is waiting infinitely in a semphore. Is there a way to determine, in
which semaphore the particular thread is waiting and which thread(s)
is holding the semaphore. (5 Replies)
Discussion started by: ptprabu
5 Replies
3. Solaris
when I tried to debug my application i got the following.
gdb -v
GNU gdb 6.6
file is in C and Xmotiff Languages
(gdb) attach 25499
Attaching to process 25499
Retry #1:
Retry #2:
Retry #3:
Retry #4:
0xfea40b68 in ?? ()
(gdb) where
#0 0xfea40b68 in ?? () (0 Replies)
Discussion started by: satish@123
0 Replies
4. Programming
Hi i want to debug the C program with GDB debugger. I want to debug the program by line by line. I want to debug program like as we debug the program in Turbo-C using the F8. Can any one help me?
I know i have to use single stepping. But i don't know how to use it. Any help can be appreciated..... (5 Replies)
Discussion started by: ps_sach
5 Replies
5. Shell Programming and Scripting
is there any way you can add a breakpoint in a script so you can stop on it?
i have used -xv in my shebang but the script just runs and i want it to stop at a specific point in the script.
appreciate any help. (1 Reply)
Discussion started by: npatwardhan
1 Replies
6. Programming
hey
i have a problem with a switch case in program and the debugger is messy has hell ( we use normal VI and gdb in our schoool to make it more diffiacult)
any way i have a problom where for some unknown reason the debugger just skips a switch statment as if it wasent even there
the rest... (2 Replies)
Discussion started by: gotenxds
2 Replies
7. Shell Programming and Scripting
So here I have a simple function that I wish to debug. However, I am unable to debug the desired function even with set -o functrace enabled. Before resorting to asking this question, I had managed to find a possible solution that did not produce the desired results, which is located here.
How... (5 Replies)
Discussion started by: BrandonD
5 Replies
8. HP-UX
Hi,
I wanted to configure new iscsi port on HPUX system, i added the target port address and configured it, once done, went to array side and searched for that host iqn number , but was nt able to find the same, came to host, then when i ran "iscsiutil -pVS" command it gave me below result
... (0 Replies)
Discussion started by: Vinay Kumar D
0 Replies
9. UNIX for Beginners Questions & Answers
I am VERY much a neophyte with shell scripting. I am working on the following,
"Create a script sends an email message to the user specified on the command line if any of the file
systems at more than 60% of capacity. The script should not process special file systems as /proc on
the... (2 Replies)
Discussion started by: doghouse308
2 Replies
LEARN ABOUT PLAN9
dh_auto_clean
DH_AUTO_CLEAN(1) Debhelper DH_AUTO_CLEAN(1)
NAME
dh_auto_clean - automatically cleans up after a build
SYNOPSIS
dh_auto_clean [buildsystemoptions] [debhelperoptions] [--params]
DESCRIPTION
dh_auto_clean is a debhelper program that tries to automatically clean up after a package build. It does so by running the appropriate
command for the build system it detects the package uses. For example, if there's a Makefile and it contains a distclean, realclean, or
clean target, then this is done by running make (or MAKE, if the environment variable is set). If there is a setup.py or Build.PL, it is
run to clean the package.
This is intended to work for about 90% of packages. If it doesn't work, or tries to use the wrong clean target, you're encouraged to skip
using dh_auto_clean at all, and just run make clean manually.
OPTIONS
See "BUILD SYSTEM OPTIONS" in debhelper(7) for a list of common build system selection and control options.
-- params
Pass params to the program that is run, after the parameters that dh_auto_clean usually passes.
SEE ALSO
debhelper(7)
This program is a part of debhelper.
AUTHOR
Joey Hess <joeyh@debian.org>
11.1.6ubuntu2 2018-05-10 DH_AUTO_CLEAN(1)