08-31-2010
Just use the run command followed by the arguments you want to pass.
9 More Discussions You Might Find Interesting
1. Programming
Which is better??
I have always been a gdb fan.. But ppl say dbx is beter better for debugging the core.. Do all GDB lovers agree to it???
:cool: (1 Reply)
Discussion started by: jyotipg
1 Replies
2. Programming
Is it possible to use the dbx debugger with the CL options for the executable ?
Say you have created a executable called myfunc which can take string arguments at run-time. You run it like this
./myfunc Hello World
where Hello and World are the string arguments
My question is whether... (1 Reply)
Discussion started by: JamesGoh
1 Replies
3. Programming
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
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. Programming
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
6. 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
7. Shell Programming and Scripting
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
8. UNIX for Dummies Questions & Answers
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
9. Programming
GNU insight debugger is not available now a days and it is required to debug/inspect
assembly code as written in the book Assembly Language Programming step by step in Linux so my question is; is there any alternative to insight that I can use instead of insight in which I can get the same... (5 Replies)
Discussion started by: vectrum
5 Replies
LEARN ABOUT DEBIAN
avr-run
run(1) GNU Tools run(1)
NAME
run--Simulator front-end
SYNOPSIS
run [-v] [-p freq] [-m memory] [--sysroot filepath] program
DESCRIPTION
Use `run program' to execute a binary by interpreting machine instructions on your host computer.
run is the same emulator used by GDB's `target sim' command. You can run it directly by executing run if you just want to see your program
execute, and do not need any debugger functionality. You can also use run to generate profiling information for analysis with gprof.
OPTIONS
-v Verbose output. Display the name of the program to run before execution; after execution, display the number of instructions exe-
cuted, the number of machine cycles emulated, the number of pipeline stalls, the real time taken, the emulated execution time taken,
and a summary of how much profiling information was generated.
-p freq
Generate profile information (for use with gprof). freq is the profiling frequency. Write the profiling information to a file
called gmon.out.
-m memory
Set the memory size for the emulated machine to two to the power memory. The default value is 19, emulating a board with 524288
bytes of memory.
--sysroot filepath
Prepend filepath to all simulator system calls that pass absolute file paths. Change working directory to filepath at program
start. Not all simulators support this option; those that don't, will ignore it.
SEE ALSO
`gprof' entry in info; `gdb' entry in info; Using GDB: A Guide to the GNU Source-Level Debugger, Richard M. Stallman and Roland H. Pesch.
COPYING
Copyright (c) 1993, 2000, 2012 Free Software Foundation, Inc.
This document is distributed under the terms of the GNU Free Documentation License, version 1.1. That license is described in the sources
for this manual page, but it is not displayed here in order to make this manual more consise. Copies of this license can also be obtained
from: http://www.gnu.org/copyleft/.
GNU Tools 13oct1993 run(1)