1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
|
[Please use the PRF form below to submit bug reports, problem
reports, etc., to the CIAO developers and interested users.
Send to ciao-users@cs.wustl.edu. If you are using OCI or PrismTech's
versions of CIAO do not send bugs to this mailing list, but
instead contact those companies for support. Please also send your
PRF as plain ASCII text, _not_ uuencoded or as an attachment.
We prefer that all bug reports be submitted through our bug tracking
system. See $ACE_ROOT/docs/usage-bugzilla.html for more information
about how to do this. If you are unsure as to whether your problem
is a real bug or not then please submit your question to the mailing
list using the following form. Not using the problem report form
will make it harder or impossible to identify the problem, and in
many cases we will be unable to help at all. Also please try to
browse bugzilla and the ChangeLog files to find out if your problem
has been solved in a more recent version of CIAO.
To ensure that you see responses, please do one of the following:
1) Subscribe to the ciao-users mail list, by sending email with
contents "subscribe ciao-users" to majordomo@cs.wustl.edu.
2) Or, monitor the comp.soft-sys.ace newsgroup for responses.
Replace/remove all the explanatory text in brackets before mailing.
Please send this form as ASCII text only. Do _not_ send it as an
attachment, or as tar'ed, compressed and/or uuencoded text. And
limit line lengths to less than 80 characters.
PLEASE make your Subject: line as descriptive as possible.
Subjects like "CIAO bug" or "bug report" are not helpful!
Also, do _not_ include the word "help" in the Subject!]
When including your config.h and platform_macros.GNU files as requested
below, only include the contents if you use the recommended method of
including the platform-specific file in your file. If you use a link
to the platform-specific file, simply state which one - DO NOT include
an entire platform-specific configuration file in the form.
8<----------8<----------8<----------8<----------8<----------8<----------8<----
To: ciao-users@cs.wustl.edu
Subject: [area]: [synopsis]
CIAO VERSION: 0.5.6
TAO VERSION : 1.5.6
ACE VERSION : 5.5.6
HOST MACHINE and OPERATING SYSTEM:
If on Windows based OS's, which version of WINSOCK do you
use?:
TARGET MACHINE and OPERATING SYSTEM, if different from HOST:
COMPILER NAME AND VERSION (AND PATCHLEVEL):
THE $ACE_ROOT/ace/config.h FILE [if you use a link to a platform-
specific file, simply state which one]:
THE $ACE_ROOT/include/makeinclude/platform_macros.GNU FILE [if you
use a link to a platform-specific file, simply state which one
(unless this isn't used in this case, e.g., with Microsoft Visual
C++)]:
CONTENTS OF $ACE_ROOT/bin/MakeProjectCreator/config/default.features
(used by MPC when you generate your own makefiles):
AREA/CLASS/EXAMPLE AFFECTED:
[What example failed? What module failed to compile?]
DOES THE PROBLEM AFFECT:
COMPILATION?
If so, what do your $ACE_ROOT/ace/config.h and
$ACE_ROOT/include/makeinclude/platform_macros.GNU contain?
LINKING?
On Unix systems, did you run make realclean first?
EXECUTION?
OTHER (please specify)?
[Please indicate whether ACE/TAO/CIAO, your application, or both are affected.]
SYNOPSIS:
[Brief description of the problem]
DESCRIPTION:
[Detailed description of problem. Don't just say "<blah>
doesn't work, here's a fix," explain what your program does
to get to the <blah> state. ]
REPEAT BY:
[What you did to get the error; include test program or session
transcript if at all possible. ]
SAMPLE FIX/WORKAROUND:
[If available ]
|
