Sponsored Content
Full Discussion: ksh bug?
Top Forums UNIX for Advanced & Expert Users ksh bug? Post 302876068 by alister on Thursday 21st of November 2013 02:22:26 PM
Old 11-21-2013
Quote:
Originally Posted by MadeInGermany
Then let's call it a shortcoming.
It looks like -x mode uses stderr, and can conflict with redirection in the shell code.
It can get messy, yes.

This is also an issue for bash ...
Code:
$ bash -xc 'echo foo; exec 2>&1; echo bar' > stdout
+ echo foo
+ exec
$ cat stdout
foo
+ echo bar
bar

... but since it does not trace redirections, the destination of the trace won't change mid-command.

Quote:
Originally Posted by MadeInGermany
Then, why stderr and not another file descriptor?
I would assume because stderr is known to be reserved for diagnostic and error messages, not data. If an alternative file descriptor were chosen, the possibility for a collision would still exist.

Corona688 makes an excellent point:
Quote:
Originally Posted by Corona688
Being 'clever' about it would make obvious things, like redirecting a trace's output into a file, difficult.
Cleverness would include attempting to detect and handle a collision between the internal tracing descriptor and a script's redirections.

Regards,
Alister

Last edited by alister; 11-21-2013 at 03:36 PM..
 

7 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Sed bug in OS X?

I've been playing around with sed for a few days now and find that regular expressions never work inside sed s/// on Mac OS 10.2.5. Has anyone else bumped up against this problem? For example, the "sed" segment of the following always fails no matter how items are escaped: cd... (12 Replies)
Discussion started by: ktoz
12 Replies

2. UNIX for Advanced & Expert Users

ksh read bug in HPUX 11i

Is this a bug in ksh on HPUX 11i or is read impromperly documented? INPUT Thu Jan 18 09:14:52 PST : CIFS: Virus Detected - File ONTAP_ADMIN$\vol\vol0\DDD\Ventana\Strattoni\Race Stuff\Rumor.exe in share DDD accessed by client CLIENT (111.11.11.111) running as user USER is infected. The filer... (3 Replies)
Discussion started by: Jackaroe
3 Replies

3. Shell Programming and Scripting

Is it a bug ..?

Hi All, I am using Red Hat Linux on my servers. The problem that I am facing is, sometimes the /opt usage on the server shows used percentage as 100% , when actually it is simply 20%. When I reboot the system, it comes back to 20%.Is this a bug in the system or my settings have gone wrong... (1 Reply)
Discussion started by: nua7
1 Replies

4. AIX

bug in 43 ???

xxxxserver# lsattr -El inet0 | grep 255.240.0.0,32.224.0.0,32.78.120.254 | grep '.40' route net,-hopcount,1,-netmask,255.240.0.0,32.224.0.0,32.78.120.254 How this is possible? (1 Reply)
Discussion started by: itik
1 Replies

5. UNIX for Dummies Questions & Answers

where's the bug?

#!/bin/bash if then #echo "infinite loop" exit 0 fi when I run this file I get the following error: ./test_infinite_loop: line 5: syntax error near unexpected token `fi' ./test_infinite_loop: line 5: `fi' :confused: (4 Replies)
Discussion started by: jon80
4 Replies

6. Shell Programming and Scripting

KSH script to run other ksh scripts and output it to a file and/or email

Hi I am new to this Scripting process and would like to know How can i write a ksh script that will call other ksh scripts and write the output to a file and/or email. For example ------- Script ABC ------- a.ksh b.ksh c.ksh I need to call all three scripts execute them and... (2 Replies)
Discussion started by: pacifican
2 Replies

7. Programming

is this a bug of g++?

Hello, Im using the g++(g++ Ubuntu/Linaro 4.4.4-14ubuntu5 4.4.5) and im trying to compile a small snippet code and got into an endless loop.I recompiled that in VS2010 under Windows 7 and the answer is as expected.so i wonder is this a bug of g++?here is my code. #include<iostream> using... (5 Replies)
Discussion started by: homeboy
5 Replies
GROFF_TRACE(7)						 Miscellaneous Information Manual					    GROFF_TRACE(7)

NAME
groff_trace - groff macro package trace.tmac SYNOPSIS
groff -m trace [options ...] [files ...] DESCRIPTION
The trace macro package of groff(1) can be a valuable tool for debugging documents written in the roff formatting language. A call stack trace is protocolled on standard error, this is, a diagnostic message is emitted on entering and exiting of a macro call. This greatly eases to track down an error in some macro. This tracing process is activated by specifying the groff or troff command line option -m trace. This works also with the groffer(1) viewer program. A finer control can be obtained by including the macro file within the document by the groff macro call .mso trace.tmac. Only macros that are defined after this line are traced. If command line option -r trace-full=1 is given (or if this register is set in the document), number and string register assignments together with some other requests are traced also. If some other macro package should be traced as well it must be specified after -m trace on the command line. The macro file trace.tmac is unusual because it does not contain any macros to be called by a user. Instead, the existing macro definition and appending facilities are modified such that they display diagnostic messages. EXAMPLES
In the following examples, a roff fragment is fed into groff via standard input. As we are only interested in the diagnostic messages (standard error) on the terminal, the normal formatted output (standard output) is redirected to the nirvana device /dev/null. The result- ing diagnostic messages are displayed directly below the corresponding example. Command line option Example: sh# echo '. > .de test_macro > .. > .test_macro > .test_macro some dummy arguments > ' | groff -m trace >/dev/null *** .de test_macro *** de trace enter: .test_macro *** trace exit: .test_macro *** de trace enter: .test_macro "some" "dummy" "arguments" *** trace exit: .test_macro "some" "dummy" "arguments" The entry and the exit of each macro call is displayed on the terminal (standard output) -- together with the arguments (if any). Nested macro calls Example: sh# echo '. > .de child > .. > .de parent > .child > .. > .parent > ' | groff -m trace >/dev/null *** .de child *** .de parent *** de trace enter: .parent *** de trace enter: .child *** trace exit: .child *** trace exit: .parent This shows that macro calls can be nested. This powerful feature can help to tack down quite complex call stacks. Activating with .mso Example: sh# echo '. > .de before > .. > .mso trace.tmac > .de after > .. > .before > .after > .before > ' | groff >/dev/null *** de trace enter: .after *** trace exit: .after Here, the tracing is activated within the document, not by a command line option. As tracing was not active when macro before was defined, no call of this macro is protocolled; on the other hand, the macro after is fully protocolled. PROBLEMS
Because trace.tmac wraps the .de request (and its cousins), macro arguments are expanded one level more. This causes problems if an argu- ment contains four backslashes or more to prevent too early expansion of the backslash. For example, this macro call .foo \\n[bar] normally passes `\n[bar]' to macro `.foo', but with the redefined .de request it passes ` [bar]' instead. The solution to this problem is to use groff's E escape which is an escape character not interpreted in copy mode, for example .foo En[bar] FILES
The trace macros are kept in the file trace.tmac located in the tmac directory; see groff_tmac(5) for details. ENVIRONMENT
$GROFF_TMAC_PATH A colon-separated list of additional tmac directories in which to search for macro files; see groff_tmac(5) for details. AUTHOR
Copyright (C) 2002, 2006, 2007, 2008 Free Software Foundation, Inc. This document is distributed under the terms of the FDL (GNU Free Documentation License) version 1.1 or later. You should have received a copy of the FDL on your system, it is also available on-line at the GNU copyleft site <http://www.gnu.org/copyleft/fdl.html>. This document is part of groff, the GNU roff distribution. It was written by Bernd Warken. SEE ALSO
groff(1) An overview of the groff system. troff(1) For details on option -m. groffer(1) A viewer program for all kinds of roff documents. groff_tmac(5) A general description of groff macro packages. groff(7) A short reference for the groff formatting language. A complete reference for all parts of the groff system is found in the groff info(1) file. Groff Version 1.21 25 June 2012 GROFF_TRACE(7)
All times are GMT -4. The time now is 03:20 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy