3 # $Log: errorList.tcl,v $
4 # Revision 1.8 1995/11/03 21:15:48 naim
5 # Chaning message of error 11 - naim
7 # Revision 1.7 1995/10/30 23:09:43 naim
8 # Modifing error message 11 - naim
10 # Revision 1.6 1995/10/12 19:45:52 naim
11 # Adding some more error messages and modifying existing ones - naim.
13 # Revision 1.5 1995/10/06 19:51:41 naim
14 # Changing default message for error 59 and adding a few more error messages
17 # Revision 1.4 1995/09/26 20:32:20 naim
18 # Fixing duplicated error messages and adding new error messages.
20 # Revision 1.3 1994/11/03 17:47:19 karavan
21 # more errors (less frequent :)
23 # Revision 1.32 1994/11/03 04:38:47 karavan
26 # Revision 1.31 1994/11/02 23:47:17 karavan
29 # Revision 1.30 1994/11/02 23:41:51 karavan
32 # Revision 1.29 1994/09/13 20:50:58 karavan
35 # Revision 1.28 1994/09/13 20:48:39 karavan
38 # Revision 1.27 1994/09/13 20:44:06 karavan
41 # Revision 1.26 1994/07/12 16:58:43 newhall
44 # Revision 1.25 1994/07/12 16:52:14 newhall
47 # Revision 1.24 1994/07/12 16:46:42 newhall
50 # Revision 1.23 1994/07/11 22:22:11 newhall
53 # Revision 1.22 1994/07/11 22:09:02 newhall
56 # Revision 1.21 1994/07/11 21:35:42 newhall
59 # Revision 1.20 1994/07/11 21:31:31 newhall
60 # *** empty log message ***
62 # Revision 1.19 1994/07/11 21:14:26 newhall
65 # Revision 1.18 1994/07/11 20:48:38 newhall
68 # Revision 1.17 1994/07/11 20:47:15 newhall
71 # Revision 1.16 1994/07/08 21:27:11 jcargill
72 # Deleted 3 bogus test errors
74 # Revision 1.15 1994/07/08 21:23:43 jcargill
77 # Revision 1.14 1994/07/08 21:19:18 jcargill
80 # Revision 1.13 1994/07/08 21:14:07 jcargill
83 # Revision 1.12 1994/07/08 03:02:56 karavan
86 # Revision 1.11 1994/07/08 02:52:55 karavan
89 # Revision 1.10 1994/04/22 21:51:17 hollings
92 # Revision 1.9 1994/04/22 21:48:54 hollings
95 # Revision 1.8 1994/04/19 18:59:35 hollings
98 # Revision 1.7 1994/04/19 18:54:43 hollings
101 # Revision 1.6 1994/04/19 18:50:06 hollings
104 # Revision 1.5 1994/04/19 18:46:30 hollings
107 # Revision 1.4 1994/04/19 18:41:55 hollings
110 # Revision 1.3 1994/04/19 18:37:43 hollings
113 # Revision 1.2 1994/04/19 18:29:48 hollings
116 # Revision 1.1 1994/04/19 18:26:56 hollings
117 # Libray of error numbers in paradyn.
122 # Error message format:
123 # set pdError(1) { -> Error number
125 # { Default error message -> Error message to be displayed when "" is received
126 # as a parameter. Detailed information such as
127 # specific filenames will be displayed only if this
128 # information was included as part of the error
130 # } {source -> Indicates where the error comes from. "source" can be:
131 # paradynd = paradyn daemon
132 # pc = performance consultant
134 # vi = visi interface
136 # ui = user interface
137 # } {error type -> information, serious, fatal
139 # Explanation -> Detailed explanation of the error and possible actions to be
144 # showErrorCallback(27, "Executable file /p/paradyn/weird not found");
149 {Application Process found for machine without paradynd
153 An application process was found to be running on a machine that had no
154 paradynd process running. This is a serious error that indicates either a
155 paradynd process could not be started, or that it might have died. This
156 error should be considered an indication of a bug in the tool.
160 {Data for unknown metric id
164 Data has arrived from a paradynd process for an unknown metric id. This is
165 a serious error that indicates a bug in the paradyn/paradynd interface.
169 {Unable to find metric component for sample.
173 A sample value has arrive for a metric from a paradynd, but the paradyn
174 process was not expecting a value from this process. This is a serious internal
175 consistency failure of the paradyn/paradynd interface.
179 {Unable to connect to new paradyn daemon process.
183 A request had arrived to start a new paradyn daemon process on a remote
184 machine (either from the user or the system based on adding new hosts), and
185 the paradyn user process was unable to rendezvous with the paradynd process.
186 This could indicate a network failure, the paradynd process not being
187 installed on the remote machine, or a file permission problem.
191 {paradynd process has died
195 A paradynd process has died somewhere in the system. This indicates either
196 a network failure, a host failure, or a bug in the paradynd process.
200 {Unable to start paradynd
204 A request to start a new application process on a machine required that a new
205 paradyn daemon process be started on that machine. The attempt to start that
206 new paradynd process failed. This is a continuable error, but does mean that
207 the request application process will NOT be started. This error can happen
208 if the path for the paradynd is incorrect, if the paradynd binary is not
209 installed on that machine, or if the machine or network is down.
213 {Auto refinement already enabled
217 An attempt to enable automatic refinement was made will automated refinement
218 was already being attempted.
222 {Unable to find search history graph node
226 An attempt to lookup a search history graph node failed. The passed integer
227 name of the node was not found in the list of nodes.
232 {Search history graph ancestor not true
236 An attempt to set the current refinement to a node failed because one of the
237 ancestors of that node is false. To manually select a SHG node, you must
238 select a node which is true. In addition, all of it's ancestors back to
239 the root must also be true.
247 Call to malloc failed within a data manager function.
251 {Application process has exited
255 An application process has exited. This situation may be produced, for example, by an unsuccessful request of memory made by this process, or it could be possible that the application just finished.
259 {malloc failed in VISIthreadchooseMetRes
263 Call to malloc failed within a visi-thread function.
267 {thr_getspecific failed
271 Call to thr_getspecific in a visi-thread function failed.
275 {Unable to start visualization process
279 A request to start a new visualization process has failed. Some possible
280 explanations are: (1) the executable for this visi is not well installed,
281 and you should check whether the executable is in the right place;
282 (2) the process you just started is not a visi process.
286 {Unable to create performance stream
290 An attempt to create a performance stream for a new visualization failed.
298 Possible causes: bufferSize out of range in VISIthreadDataCallback and remove() in VISIthreadmain. Please, report this error to paradyn@cs.wisc.edu
302 {Adding new metrics and/or foci failed
306 An incomplete or invalid metric or focus list was returned as a result of
307 attempting to add metrics and/or foci to a visualization.
311 {malloc failure in visi manager
315 Call to malloc failed within a visi manager function.
323 Call to strdup failed within a visi manager function.
331 An unrecoverable error occurred within a visi manager function. Please,
332 report this error to paradyn@cs.wisc.edu
340 The tcl interpreter has failed. Bad pointer "newptr". Please, report
341 this error to paradyn@cs.wisc.edu
349 The tcl interpreter has failed unexpectedly (getMetsAndRes in UIM::chooseMetricsandResources). Please, report this error to paradyn@cs.wisc.edu
357 Read error in application process.
361 {Unable to read tcl start-up script
365 A tcl error occurred finding or reading the tcl script specified on the
366 paradyn command line with the -s option.
370 {Unable to define specified process
374 An error occurred while attempting to define an application.
378 {tcl initialization for new resource display object failed.
382 Call to tcl command initRDO failed.
386 {Executable not found.
390 The executable you are trying to run does not exist. Check out your filename
395 {Unable to find symbol.
399 Sorry, no more information available.
403 {Function has bad address.
407 Sorry, no more information available.
411 {Incorrect version number.
415 Sorry, no more information available.
419 {Internal symbol DYNINSTfirst not found.
423 You have not properly linked your application with the paradyn dyninst library.
424 Please, refer to the manual pages in order to check how to do this.
428 {Internal symbol DYNINSTend not found.
432 This is an internal error. Please, report it to paradyn@cs.wisc.edu
436 {Could not find version number in instrumentation.
440 Your program has been linked with the wrong version of the paradyn dyninst
445 {Error function without module.
449 Sorry, no more information available.
453 {Unable to open PIF file.
457 Sorry, no more information available.
461 {Internal error: non-aligned length received on traceStream.
465 Please, report this error to paradyn@cs.wisc.edu
469 {Internal error: wrong record type on sid
473 Internal error. Please, report this error to paradyn@cs.wisc.edu
477 {Error in forwarding signal
481 Internal error. Please, report this error to paradyn@cs.wisc.edu
485 {Internal error: unknown process state
489 Internal error. Please, report this error to paradyn@cs.wisc.edu
493 {Internal error: unable to detach PID
497 Internal error. Please, report this error to paradyn@cs.wisc.edu
501 {Unable to open file.
505 Sorry, no more information available.
509 {Internal error: unable to parse executable.
513 Internal error. Please, report this error to paradyn@cs.wisc.edu
517 {Internal error: unable to get loader info about process.
521 Internal error. Please, report this error to paradyn@cs.wisc.edu
525 {Internal error: error reading header
529 Internal error. Please, report this error to paradyn@cs.wisc.edu
533 {Internal error: problem with executable header file.
537 Internal error. Please, report this error to paradyn@cs.wisc.edu
541 {Program not statically linked.
545 Sorry, no more information available.
549 {dumpcore not available yet.
553 Sorry, no more information available.
557 {Symbol table out of order, use -Xlinker -bnoobjreorder
561 Sorry, no more information available.
565 {Error reading executable file.
569 Sorry, no more information available.
573 {Internal error: Cannot find file in inst-power.C
577 Internal error. Please, report this error to paradyn@cs.wisc.edu
581 {Internal error: In forkNodeProcesses, parent id unknown.
585 Internal error. Please, report this error to paradyn@cs.wisc.edu
589 {Internal error: Branch too far.
593 Internal error. Please, report this error to paradyn@cs.wisc.edu
597 {Internal error: Program text + data is too big for dyninst.
601 Internal error. Please, report this error to paradyn@cs.wisc.edu
605 {Warning: Program text + data could be too big for dyninst.
609 Sorry, no more information available.
613 {Internal error: Unsupported return.
617 Internal error. Please, report this error to paradyn@cs.wisc.edu
621 {Internal error: exec failed in paradynd to start paradyndCM5.
625 Internal error. Please, report this error to paradyn@cs.wisc.edu
629 {Internal error: could not write all bytes.
633 Internal error. Please, report this error to paradyn@cs.wisc.edu
637 {Internal error: unable to find process.
641 Internal error. Please, report this error to paradyn@cs.wisc.edu
645 {Internal error: there are no processes known to this daemon.
649 Internal error. Please, report this error to paradyn@cs.wisc.edu
653 {Internal error: unable to find thread.
657 Internal error. Please, report this error to paradyn@cs.wisc.edu
661 {Internal error: disableDataCollection mid not found.
665 Internal error. Please, report this error to paradyn@cs.wisc.edu
669 {Internal error: cannot continue PID.
673 Internal error. Please, report this error to paradyn@cs.wisc.edu
677 {Internal error: cannot pause PID.
681 Internal error. Please, report this error to paradyn@cs.wisc.edu
685 {No function calls in procedure.
689 No function calls where found in current procedure.
693 {Sample not for valid metric instance.
697 Sorry, no more information available.
701 {Internal error: inferior heap overflow.
705 Internal error. Please, report this error to paradyn@cs.wisc.edu
709 {Internal error: attempt to free already freed heap entry.
713 Internal error. Please, report this error to paradyn@cs.wisc.edu
717 {Internal error: unable to start file.
721 Sorry, no more information available.
725 {Internal error: ptrace error.
729 Internal error. Please, report this error to paradyn@cs.wisc.edu
733 {Internal error: execv failed.
737 Internal error. Please, report this error to paradyn@cs.wisc.edu
741 {Internal error: vfork failed.
745 Internal error. Please, report this error to paradyn@cs.wisc.edu
749 {Internal error: unable to stat.
753 Internal error. Please, report this error to paradyn@cs.wisc.edu
757 {Internal error: could not (un)marshall parameters, dumping core.
761 Internal error. Please, report this error to paradyn@cs.wisc.edu
765 {Internal error: protocol verification failed.
769 Internal error. Please, report this error to paradyn@cs.wisc.edu
773 {Internal error: cannot do sync call.
777 Internal error. Please, report this error to paradyn@cs.wisc.edu
781 {Internal error: unknown message tag.
785 Internal error. Please, report this error to paradyn@cs.wisc.edu
789 {Internal error: handle error called for wrong err_state.
793 Internal error. Please, report this error to paradyn@cs.wisc.edu
797 {Internal error: problem stopping process.
801 Internal error. Please, report this error to paradyn@cs.wisc.edu
805 {Internal error: unable to find addr of DYNINSTobsCostLow.
809 Internal error. Please, report this error to paradyn@cs.wisc.edu
813 {Internal error: unable to find addr of callee process.
817 Internal error. Please, report this error to paradyn@cs.wisc.edu
821 {Cannot start process on specified host.
825 This error maybe produced by a wrong host name. Paradyn cannot create the
826 process on the host you are specifying.
830 {Trying to run a thread that is not ready yet.
834 You are trying to run a process that it is still being created. Please, wait
839 {Internal error: Tcl interpreter failed in routine changeApplicState.
843 Internal error. Please, report this error to paradyn@cs.wisc.edu
847 {Cannot create new paradyn daemon process.
851 An error was detected when a paradyn daemon was being created. Possible
852 explanations for this problem are: (1) unknown host; (2) it is not possible
853 to establish connection with the specified host.