Re: [ace-users] ACE: TRACE
Douglas C. Schmidt
hi Parimal,
Thanks very much for your email. Please make sure to send all
questions related to TAO or ACE to the ACE mailing list or ACE+TAO
newsgroup, rather than to me directly since I travel frequently and
often don't have ready access to email. See
http://www.cs.wustl.edu/~schmidt/ACE-mail.html
for more info on how to access these resources.
In addition, to ensure that we have proper version/platform/compiler
information, please make sure you fill out the appropriate problem
report form (PRF), which is in
$ACE_ROOT/PROBLEM-REPORT-FORM
$TAO_ROOT/PROBLEM-REPORT-FORM
or in
$ACE_ROOT/BUG-REPORT-FORM
$TAO_ROOT/BUG-REPORT-FORM
in older versions of ACE+TAO. Make sure to include this information
when asking any questions about ACE+TAO since otherwise we have to
"guess" what version/platform/compiler/options you've using, which is
very error-prone and slows down our responsiveness. If you don't use
the PRF, therefore, it is less likely that someone from the core
ACE+TAO developer team will be able to answer your question.
Naturally, we encourage and appreciate other members of the ACE+TAO
user community who can respond to questions that they have the answers
to.
> I am using ACE 5.5 for a tool development.
You're using a very old version of ACE. Please upgrade to ACE+TAO+CIAO
x.7.6 (i.e., ACE 5.7.6, TAO 1.7.6, and CIAO 0.7.6), which you can
download from
http://download.dre.vanderbilt.edu
under the heading: "Latest Micro Release Kit."
The DOC group at Vanderbilt University only provides "best effort"
support for non-sponsors for the latest release, as described in
http://www.dre.vanderbilt.edu/~schmidt/DOC_ROOT/ACE/docs/ACE-bug-process.html
Thus, if you need more "predictable" help for earlier versions of
ACE+TAO, I recommend that you check out
http://www.dre.vanderbilt.edu/support.html
for a list of companies that will provide you with ACE+TAO commercial
support.
> I have done the configuration with
> the command
> ../configure CXXFLAGS=-m32 LDFLAGS="-m32 -L/usr/lib" --enable-trace..
Please don't use configure - use the "traditional" way to build ACE,
which is described in
ACE_ROOT/ACE-INSTALL.html#unix_traditional
> I used -m32 because I needed the lib in 32 bit. and I enabled the
> trace also. Now I want am not aware where the LOG get stored. Could
> you please help me with the path of the LOG or is there any setting I
> need to do to specify the PATH ?
I'm not sure exactly what you mean, but please check out the examples of
ACE_Trace in
ACE_ROOT/examples/Misc/test_trace.cpp
Thanks,
Doug
Gopi
wrote:
>
> Thus, if you need more "predictable" help for earlier versions of
> ACE+TAO, I recommend that you check out
>
> http://www.dre.vanderbilt.edu/support.html
>
> for a list of companies that will provide you with ACE+TAO commercial
> support.
>
> > I have done the configuration with
> > the command
> > ../configure CXXFLAGS=-m32 LDFLAGS="-m32 -L/usr/lib" --enable-trace..
>
> Please don't use configure - use the "traditional" way to build ACE,
> which is described in
>
> ACE_ROOT/ACE-INSTALL.html#unix_traditional
>
> > I used -m32 because I needed the lib in 32 bit. and I enabled the
> > trace also. Now I want am not aware where the LOG get stored. Could
> > you please help me with the path of the LOG or is there any setting I
> > need to do to specify the PATH ?
>
> I'm not sure exactly what you mean, but please check out the examples of
> ACE_Trace in
>
> ACE_ROOT/examples/Misc/test_trace.cpp
>
> Thanks,
>
> Doug
Where will the ace traces (or trace output) get generated. If we go
through start_tracing function, it says syslog is where it gets
generated, but we dont see any ace traces in /var/log/messages
Douglas C. Schmidt
> Where will the ace traces (or trace output) get generated. If we go
> through start_tracing function, it says syslog is where it gets
> generated, but we dont see any ace traces in /var/log/messages
The ACE_Trace messages are sent to whereever ACE_DEBUG sends them, as
per this code in ACE_Trace's constructor:
----------------------------------------
ACE_Trace::ACE_Trace (const ACE_TCHAR *n,
int line,
const ACE_TCHAR *file)
{
#if defined (ACE_NLOGGING)
ACE_UNUSED_ARG (line);
ACE_UNUSED_ARG (file);
#endif /* ACE_NLOGGING */
this->name_ = n;
// If ACE has not yet been initialized, don't try to trace... there's
// too much stuff not yet initialized.
if (ACE_Trace::enable_tracing_ && !ACE_OS_Object_Manager::starting_up ())
{
ACE_Log_Msg *lm = ACE_LOG_MSG;
if (lm->tracing_enabled ()
&& lm->trace_active () == 0)
{
lm->trace_active (1);
ACE_DEBUG ((LM_TRACE,
ACE_TEXT ("%*s(%t) calling %s in file `%s' on line %d\n"),
ACE_Trace::nesting_indent_ * lm->inc (),
ACE_TEXT (""),
this->name_,
file,
line));
lm->trace_active (0);
}
}
}
----------------------------------------
By default, ACE_DEBUG writes messages to stderr. If that's not where
they are going then it's probably because your code has configured
ACE_DEBUG to redirect the messages elsewhere, so I recommend you look
at the code to figure out what it's doing. If you need more
predictable help, please contact one of the companies listed at
http://www.dre.vanderbilt.edu/support.html
for commercial support.
Thanks,
Doug
--
Dr. Douglas C. Schmidt Professor and Associate Chair
Electrical Engineering and Computer Science TEL: (615) 343-8197
Vanderbilt University WEB: www.dre.vanderbilt.edu/~schmidt
Nashville, TN 37203 NET: d.sc...@vanderbilt.edu