There was no count specified in your changed request in post #8. This is as close as I get towards your before last specification:
Rg. your next change in spec, I'd propose you proceed as indicated in post #9: change spec and script in small steps, understand discrepancies in result and operation, and come back with very specific, detailed questions. "Result is somewhat not as expected" doesn't help to track down errors, neither yourself nor others trying to help. "Why can't the error code value be extracted or isolated" is way more targeted, don't you think? Yes, this is tedious, but the only way to get through.
Hi All,
Iam trying to set the value to the array... Still its not happening
Following is the code:
#!/usr/bin/ksh
filenames="x";
filenames="y";
echo $filenames;
echo $filenames;
O/P:
x
x
Iam expecting (2 Replies)
Hi,
I have two Sun Fire V490 with Solaris 10 5/08, FC switch and two Sun StorageTek 3500 FC arrays. Each array is connected to switch and to one server at a time. In the last week I installed Solaris 10 5/08 on both servers and set up Sun Cluster, version 3.2. At wednesday all was fine - all... (7 Replies)
I am beginner in awk
awk 'BEGIN{for(i=1;(getline<"opnoise")>0;i++) arr=$1}{print arr}'
In the above script, opnoise is a file, I am reading it into an array and then printing the value corresponding to index 20. Well this is not my real objective, but I have posted this example to describe... (19 Replies)
Hi all,
I been looking for a solution to the fact that when I use:
for (i=1; i<=NF; i++) print $ifields that are originally in a single line are printed in a single line
I have severals files for which the first 7 are the same, but the number of variables after that can vary, for example NF... (5 Replies)
Hi,
I am unable to assign value zero to my variable which is defined as unsigned char.
typedef struct ABCD
{
unsigned char abc;
unsigned char def;
unsigned char ghi;
} ABCD;
typedef ABCD *PABCD;
In my Por*C code, i assign the values using memcpy like below
... (3 Replies)
Hi,
i have the following code in which i am passing array tldn in awk using -v option & despite of that condition is not getting matched,can somebody suggest how to handle shell arrays in awk
tcount=(9875 9667)
awk -F"\t" -v ltldn="${tldn}" 'NR==FNR {POSTPAIDMDNS=$2"|"$3;next}
... (6 Replies)
Hello,
May i please know how do i print the array using awk script. I am using below shell script to start with but not working.
#!/bin/bash
LOADSTATUS="Line 0"
LOADSTATUS="Line 1"
LOADSTATUS="Line 2"
LOADSTATUS="Line 3"
LOADSTATUS="Line 4"
awk '
BEGIN {
Your File Load Status
}... (1 Reply)
I have test.sh file as below :
set -A IDARR $ID
echo | awk -f test.awk -v TempArr="${IDARR
}"
I have test.awk file as below :
BEGIN {
Flag = 1;
}
{
print "Hello";
for(i in TempArr)
{
print i;
}
} (9 Replies)
In the below awk I am splitting $7 on the : and then counting each line or NM_xxxx. If the $1 value is the same for each line then print the $7 that occurs the most with the matching $1 value. The awk seems close but I am not sure what is going on. I included a description as well as to what I... (1 Reply)
I am unable to loop print a python string array in my unix shell script:
~/readarr.sh '{{ myarr }}'
more readarr.sh
echo "Parameter 1:"$1
MYARRAY= $1
IFS=
MYARRAY=`python <<< "print ' '.join($MYARRAY)"`
for a in "$MYARRAY"; do
echo "Printing Array: $a"
done
Can you... (10 Replies)
Discussion started by: mohtashims
10 Replies
LEARN ABOUT SUSE
tk::error
Error(3) User Contributed Perl Documentation Error(3)NAME
Tk::Error - Method invoked to process background errors
SYNOPSIS
Customization:
require Tk::ErrorDialog;
or
sub Tk::Error
{
my ($widget,$error,@locations) = @_;
...
}
DESCRIPTION
The Tk::Error method is invoked by perl/Tk when a background error occurs. Two possible implementations are provided in the distribution
and individual applications or users can (re)define a Tk::Error method (e.g. as a perl sub) if they wish to handle background errors in
some other manner.
A background error is one that occurs in a command that didn't originate with the application. For example, if an error occurs while
executing a callback specified with a bind or a after command, then it is a background error. For a non-background error, the error can
simply be returned up through nested subroutines until it reaches the top-level code in the application; then the application can report
the error in whatever way it wishes. When a background error occurs, the unwinding ends in the Tk library and there is no obvious way for
Tk to report the error.
When Tk detects a background error, it saves information about the error and invokes the Tk::Error method later when Tk is idle.
Tk::Error is invoked by perl/Tk as if by the perl code:
$mainwindow->Tk::Error("error message", location ...);
$mainwindow is the MainWindow associated with widget which detected the error, "error message" is a string describing the error that has
been detected, location is a list of one or more "locations" which describe the call sequence at the point the error was detected.
The locations are a typically a mixture of perl location reports giving script name and line number, and simple strings describing
locations in core Tk or perl/Tk C code.
Tk will ignore any result returned by the Tk::Error method. If another error occurs within the Tk::Error method (for example if it calls
die) then Tk reports this error itself by writing a message to stderr (this is to avoid infinite loops due to any bugs in Tk::Error).
If several background errors accumulate before Tk::Error is invoked to process them, Tk::Error will be invoked once for each error, in the
order they occurred. However, if Tk::Error calls Tk->break, then any remaining errors are skipped without calling Tk::Error.
The Tk module includes a default Tk::Error subroutine that simply reports the error on stderr.
Tk::ErrorDialog
An alternate definition is provided via:
"require Tk::ErrorDialog;"
that posts a dialog box containing the error message and offers the user a chance to see a stack trace showing where the error occurred.
This is an OO implementation of the Tcl/Tk command bgerror, with a twist: since there is only one ErrorDialog widget, you aren't required
to invoke the constructor to create it; it will be created automatically when the first background error occurs. However, in order to
configure the -cleanupcode and -appendtraceback ErrorDialog options you must call the constructor and create it manually.
The ErrorDialog object essentially consists of two subwidgets: a Dialog widget to display the background error and a Text widget for the
traceback information. If required, you can invoke various widget methods to customize these subwidgets - their advertised names are
described below.
$mw->ErrorDialog(-cleanupcode => code, -appendtraceback => bool);
$mw is a window reference.
code is a CODE reference if special post-background error processing is required (default is undefined). The callback subroutine is called
with @_ having the same arguments that Tk::Error was invoked with.
bool is a boolean indicating whether or not to append successive tracebacks (default is 1, do append).
Advertised ErrorDialog widgets
error_dialog is the Dialog widget reference.
text is the Text widget reference containing the traceback information.
BUGS
If after or fileevent are not invoked as methods of a widget then perl/Tk is unable to provide a $mainwindow argument. To support such
code from earlier versions of perl/Tk perl/Tk therefore calls Tk::Error with string 'Tk' instead: Tk->Tk::Error(...). In this case the
Tk::Error in Tk::ErrorDialog and similar implementations cannot "popup" a window as they don't know which display to use. A mechanism to
supply the MainWindow in applications which only have one (a very common case) should be provided.
SEE ALSO
Tk::bind Tk::after Tk::fileevent
KEYWORDS
background error, reporting
perl v5.12.1 2007-05-05 Error(3)