DL(3) Library Functions Manual DL(3)NAME
DL - generate logging messages in C and C++ using a debugger
SYNOPSIS
#include <DL.h>
DL(format,...)
DLG(guard,format,...)
DLH(handler,format,...)
DLP(param,format,...)
DLGH(guard,handler,format,...)
DLHP(handler,param,format,...)
DLGHP(guard,handler,param,format,...)
DESCRIPTION
The DL macro is used to print logging or debugging messages using a debugger. The nana(1) command generates a set of debugger commands
which are then sourced into gdb(1) to implement the logging. If you don't run the executable under gdb(1) then no tracing will occur. The
arguments are:
format,... - a printf(3) style argument list containing the message
guard - print only if the guard is true.
handler - the code that does the printing. Default: fprintf
param - a parameter to be passed off to the handler. Default: stdout
See nana.info for details on configuring the behaviour.
SEE ALSO nana-clg(1), nana(1), nana(3), I(3), DI(3), L(3), DL(3), Q(3) and nana.info.
The nana.info file is the primary documentation for this library.
AUTHOR
Phil Maker <pjm@gnu.org>
DL(3)
Check Out this Related Man Page
DI(3) Library Functions Manual DI(3)NAME
DI - verify assertions in C and C++ code using gdb(1)SYNOPSIS
#include <DI.h>
DI(exprn)
DIG(exprn,guard)
DIH(exprn,handler)
DIP(exprn,param)
DIGH(exprn,guard,handler)
DIHP(exprn,handler,param)
DIGHP(exprn,guard,handler,param)
DS(exprn)
DESCRIPTION
The DI(exprn) checks that the exprn is true in the same way as assert(3). It is however implemented by generating debugger commands from
the source code and so only works if you run the command under a debugger after source the command file generated by nana(1).
exprn - the expression to be checked.
guard - the expression is normally only checked if the guard is true.
handler - a macro which generates the code that handles the error condition.
param - a parameter which can be passed off to the handler. This can be used for identifying the assertion failure in a space-efficent man-
ner, e.g. by copying it into a register before aborting.
See nana.info for details on configuring the behaviour on error detection, etc. You also need to include the nana library by using -lnana
if you use the default setup.
In addition to the DI, DIG, etc DI.h also provides DN, DNG, etc which are used to check that an expression is never true.
SEE ALSO nana-clg(1), nana(1), nana(3), I(3), L(3), DL(3), Q(3) and nana.info.
The nana.info file is the primary documentation for this library.
AUTHOR
Phil Maker <pjm@gnu.org>
DI(3)
Hi all,
I need some info regarding which all debuggers are available for Pro-C code.
i am working on Solaris.
I had heard about 2 debuggers called 'Workshop' and GDB but then i am not sure.
pls help me out in this.
Regards
Manish (1 Reply)
Hi all,
is it possible to skip a function with the wdb debugger ?
could be helpful instead of compiling the whole bunch again
does someone know how to do this ?
thx
Sven (4 Replies)
Does Anybody know how to print procedures written in this format?
..
.nr PS 11
.nr VS 14
.nr LL 6.5i
.ad l
.DA 1/9/91
.in 4.0i
.DS
Shepard D. Johnson
.DE
.in 0i
.sp
.sp
.sp
.LG
.ce
.B
Pressure Sensors (P/N 16-0018-0 & 16-0018-1) Test Procedure (1 Reply)
Hello,
Does any one knows any tools or method to monitor users all activities on Solaris 8, including command and its result. Similar to 'script' ???
Thanks
nana (3 Replies)
In DDD debugger, where to set the the arguments for main program?
For example: ./myExe "argv1" "argv2" -> where to set "argv1" & "argv2" ?
Thanks! (2 Replies)
Hi,
can somebody advise on a better multiprocess debugger?
I heard with gdb we face lots of problems in multiprocess scenario
currently i am using gdb debugger for a single process multithreaded project..
since i am supposed to work on a multiprocess now, i googled and came across... (1 Reply)
I was analyzing the syntax on the MOV Assembly command after debugging my c code using gdb. What I don't understand is that on some machines it shows me a MOV AL,0 and on some MOV 0,AL. I know both mean the same but what is it that differentiates the syntax? (4 Replies)
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)
I ask a question about the executalbe file compiled with make. Which debugger is appropriate? I tried to use gdb. But it failed to give the code with 'list' command.
Program received signal SIGTSTP, Stopped (user).
0x0000000000472621 in DivergeTreeLogLikelihood ()
(gdb) bt
#0 ... (5 Replies)
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)
$SET_PARAMS='-param Run_Type_Parm=Month -param Portfolio_Parm="997" -param From_Date_Parm="2011-08-09"'
Want to extract the value of "Portfolio_Parm" from $SET_PARAMS i.e in the above case "997" & assigned to new variable.
The existence order of "Portfolio"Parm" can change, but the name... (2 Replies)
Hi,
I need to read two values,startdate and enddate from a param file and then write this value to another param file(global) under a specific workflow name.Here in global param file there is may workflow names, hence we need to check for the right one and then add the data below it.
Any... (5 Replies)
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)