Search the web
Sign In
New User? Sign Up
ace-bugs
  • Members Only
  • Post
  • Files
  • Photos
  • Links
  • Database
  • Polls
  • Members
  • Calendar
  • Promote
  • Groups Labs (Beta)
? Already a member? Sign in to Yahoo!

Yahoo! Groups Tips

Did you know...
Want to share photos of your group with the world? Add a group photo to Flickr.

Best of Y! Groups

   Check them out and nominate your group.
Having problems with message search? Fill out this form to ensure your group is one of the first to be migrated to the new message search system.

Messages

   Messages Help
Message #
Search:
Advanced
Messages 6142 - 6171 of 6171   Newest  |  < Newer  |  Older >  |  Oldest
Messages: Show Message Summaries   (Group by Topic) Sort by Date v  
#6171 From: "Johnny Willemsen" <jwillemsen@...>
Date: Wed Dec 9, 2009 1:52 pm
Subject: Re: ACE-core: XtReactor doesn't synchronize ACE_Reactor_Mask/XtInputMask correctly 		jwillemsen@...
Send Email Send Email
 

Hi,

 

Thanks for using the PRF form. Can you make some patches to improve the behavior and put this in bugzilla?

 

Johnny

 


ACE VERSION: 5.7

HOST MACHINE and OPERATING SYSTEM: PC Linux (SusE Enterprise 10.2)

BUILD METHOD USED: ./configure

AREA/CLASS/EXAMPLE AFFECTED: ACE_XtReactor

PROBLEM AFFECTS: EXECUTION

SYNOPSIS: XtReactor doesn't synchronize ACE_Reactor_Mask/XtInputMask correctly.

DESCRIPTION:
I'm working on a project where I've just changed the IPC to use a buffered
TCP connection. Once the connection is established I register the handler
with READ_MASK. Output is buffered in a buffer queue. Once output is
available, I register the handler with WRITE_MASK. After the data has
been written using gather write, I remove the handler using
WRITE_MASK|DONT_CALL. The X11 Application where I had the problem also used
a 1sec interval ACE_Timer.

I got the following behaviour: The application read a large amount of data
from the socket, processed it and then slept until the next timeout
ocurred. Repeat ad infinitum ...

Investigation of the ACE_XtReactor showed that the remove_handler_i
implementaion always removes the XtInputhandler for the handle,
completely ignoring the mask which was removed. Thus the removal of
of the WRITE_MASK removed the check for readability during
XtAppProcessEvent. The underlying Select_Reactor than selected the socket
for reading whenever a timeout ocurred.

BTW, the behaviour of register_handler_i is also incorrect. It replaces
an existing XtInput using the newly added mode, but doesn't take into
account the previous mode.

REPEAT BY:
Difficult, as this a pure behavioural bug and needs at least two processes
using appropriate communication patterns to reproduce.

WORKAROUND:
Always remove all currently used modes and then register the wanted mode. 

_______________________________________________
ace-bugs mailing list
ace-bugs@...
http://list.isis.vanderbilt.edu/mailman/listinfo/ace-bugs

Reply | Forward | Messages in this Topic (2)
#6170 From: dirk.bonekaemper@...
Date: Wed Dec 9, 2009 1:22 pm
Subject: ACE-core: XtReactor doesn't synchronize ACE_Reactor_Mask/XtInputMask correctly 		dirk.bonekaemper@...
Send Email Send Email
 

ACE VERSION: 5.7

HOST MACHINE and OPERATING SYSTEM: PC Linux (SusE Enterprise 10.2)

BUILD METHOD USED: ./configure

AREA/CLASS/EXAMPLE AFFECTED: ACE_XtReactor

PROBLEM AFFECTS: EXECUTION

SYNOPSIS: XtReactor doesn't synchronize ACE_Reactor_Mask/XtInputMask correctly.

DESCRIPTION:
I'm working on a project where I've just changed the IPC to use a buffered
TCP connection. Once the connection is established I register the handler
with READ_MASK. Output is buffered in a buffer queue. Once output is
available, I register the handler with WRITE_MASK. After the data has
been written using gather write, I remove the handler using
WRITE_MASK|DONT_CALL. The X11 Application where I had the problem also used
a 1sec interval ACE_Timer.

I got the following behaviour: The application read a large amount of data
from the socket, processed it and then slept until the next timeout
ocurred. Repeat ad infinitum ...

Investigation of the ACE_XtReactor showed that the remove_handler_i
implementaion always removes the XtInputhandler for the handle,
completely ignoring the mask which was removed. Thus the removal of
of the WRITE_MASK removed the check for readability during
XtAppProcessEvent. The underlying Select_Reactor than selected the socket
for reading whenever a timeout ocurred.

BTW, the behaviour of register_handler_i is also incorrect. It replaces
an existing XtInput using the newly added mode, but doesn't take into
account the previous mode.

REPEAT BY:
Difficult, as this a pure behavioural bug and needs at least two processes
using appropriate communication patterns to reproduce.

WORKAROUND:
Always remove all currently used modes and then register the wanted mode. 
DFS Deutsche Flugsicherung GmbH
Am DFS-Campus 10
D - 63225 Langen

Tel.: +49-(0)6103-707-0

Sitz der Gesellschaft: Langen/Hessen
Zuständiges Registergericht: AG Offenbach am Main, HRB 34977
Vorsitzender des Aufsichtsrates: Robert Scholl
Geschäftsführer: Dieter Kaden (Vors.), Ralph Riedle, Jens Bergmann

Internet: http://www.dfs.de
Public-Key der DFS: http://www.dfs.de/dfs/public_key.asc
_______________________________________________
ace-bugs mailing list
ace-bugs@...
http://list.isis.vanderbilt.edu/mailman/listinfo/ace-bugs

Reply | Forward | Messages in this Topic (2)
#6169 From: Koh <k_onishi@...>
Date: Sat Dec 5, 2009 2:19 pm
Subject: Re: [ACE_Timer_Wheel_T] fail to evaluate earliest spoke 		k_onishi@...
Send Email Send Email
  
Doug,

I had reported ACE_Timer_Wheel_T bug on 22 Sep 2009 ,
and I updated $ACE_ROOT/tests/Timer_Queue_Test.cpp .
When you use the file attached with the ACE 5.7.1,
it will fail because of the bug I reported.
If you modify Timer_Wheel_T.cpp line 151, it will work.


> >     Problem cause
> >     --------------
> >     Timer_Wheel_T.cpp, line 151 looks wrong.
> >     The line 151 of Timer_Wheel_T.cpp should be
> >       this->wheel_time_.msec (1 << (this->res_bits_));
> >     instead of
> >       this->wheel_time_.msec (1 << (this->res_bits_ + this->spoke_bits_));
> >     or the recalc_earliest selects wrong spoke as earliest_spoke_.
> >
> >     If the wheel_time_.msec is set with 1 << (this->res_bits_ +
this->spoke_bits_,
> >     spoke_bits_ is 10 when the default value is used,
> >     the wheel_time_ value is too long.
> >     This means the "for loop" at line 704 will select the first spoke
> >     every time when the recalc_earliest is called.
>
> Thanks for reporting this - I've updated the code.  Could you please
> help out ingUpdate the ACE_ROOT/tests/Timer_Queue_Test.cpp regression
> test to illustrate the problem?  This way, we can ensure that the
> implementation continues to work.
>
> thanks,
>
>         Doug

Best Regards,
Koh
_______________________________________________
ace-bugs mailing list
ace-bugs@...
http://list.isis.vanderbilt.edu/mailman/listinfo/ace-bugs

Reply | Forward | Messages in this Topic (4)
#6168 From: "Douglas C. Schmidt" <schmidt@...>
Date: Thu Nov 19, 2009 8:32 pm
Subject: Re: ACE_Log_Msg_NT_Event_Log not able log a large string 		schmidt@...
Send Email Send Email
  
Hi Gaurav,

> I have rebuilt ace with the following 2 changes:
>
> 1. Changed the value ACE_MAXLOGMSGLEN in config.h from 192 to 192*4 (can't
have default 1024*4 for performance reasons)
> 2. Changed the ACE_Log_Msg_NT_Event_Log::log implementation to take care of
msg_data size (in case it is greater than ACE_Log_Record::MAXLOGMSGLEN).
>
> ssize_t
> ACE_Log_Msg_NT_Event_Log::log (ACE_Log_Record &log_record)
> {
>
>   const ACE_TCHAR* src_msg_data = log_record.msg_data ();
>   ACE_TCHAR msg_data [(ACE_Log_Record::MAXLOGMSGLEN * 2)+1];
>
>   size_t k=ACE_Log_Record::MAXLOGMSGLEN ;
>   if(ACE_Log_Record::MAXLOGMSGLEN > log_record.msg_data_len () )
> 	  k=log_record.msg_data_len ();
>
>   size_t p=0;
>   for (size_t i = 0, j = 0;
>        i < k;
>        ++i)
>     {
>       if (src_msg_data[i] == '\n')
>         {
>           msg_data[j++] = '\r';
>           msg_data[j++] = '\n';
>         }
>       else
>         msg_data[j++] = src_msg_data[i];
>
> 	  p=j;
>     }
>  msg_data[p]='\0';
>
> same old code....
>
> }
>
> It works fine for all the strings length.

Great, thanks!  I changed some of the variable names.  Please see

http://www.dre.vanderbilt.edu/~schmidt/DOC_ROOT/ACE/ace/Log_Msg_NT_Event_Log.cpp

and let me know if this still works for you.

Thanks,

         Doug
_______________________________________________
ace-bugs mailing list
ace-bugs@...
http://list.isis.vanderbilt.edu/mailman/listinfo/ace-bugs

Reply | Forward | Messages in this Topic (11)
#6167 From: Gaurav Kulshreshtha <gaurav.kulshreshtha@...>
Date: Thu Nov 19, 2009 10:05 am
Subject: Re: ACE_Log_Msg_NT_Event_Log not able log a large string 		gaurav.kulshreshtha@...
Send Email Send Email
  
------=neXtPaRt_1258625903
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi Douglas,

I have rebuilt ace with the following 2 changes:

1. Changed the value ACE_MAXLOGMSGLEN in config.h from 192 to 192*4 (can't have
default 1024*4 for performance reasons)
2. Changed the ACE_Log_Msg_NT_Event_Log::log implementation to take care of
msg_data size (in case it is greater than ACE_Log_Record::MAXLOGMSGLEN).

ssize_t
ACE_Log_Msg_NT_Event_Log::log (ACE_Log_Record &log_record)
{

   const ACE_TCHAR* src_msg_data = log_record.msg_data ();
   ACE_TCHAR msg_data [(ACE_Log_Record::MAXLOGMSGLEN * 2)+1];

   size_t k=ACE_Log_Record::MAXLOGMSGLEN ;
   if(ACE_Log_Record::MAXLOGMSGLEN > log_record.msg_data_len () )
	   k=log_record.msg_data_len ();

   size_t p=0;
   for (size_t i = 0, j = 0;
        i < k;
        ++i)
     {
       if (src_msg_data[i] == '\n')
         {
           msg_data[j++] = '\r';
           msg_data[j++] = '\n';
         }
       else
         msg_data[j++] = src_msg_data[i];

	   p=j;
     }
	 msg_data[p]='\0';

same old code....

}

It works fine for all the strings length.

Regards,
Gaurav



-----Original Message-----
From: Douglas C. Schmidt [mailto:schmidt@...]
Sent: Wednesday, November 18, 2009 8:14 PM
To: Gaurav Kulshreshtha; ace-bugs@...; chris@...
Subject: Re: [ace-bugs] ACE_Log_Msg_NT_Event_Log not able log a large string

Hi Gaurav,

>I am aware that using the ACE_Log_Msg_NT_Event_Log without open will not wo=
>rk (sample code). I was only concerned about the logged string size in case=
> of crash.
>After debugging I found out what part of the code is causing the problem. M=
>aximum size of a logged string is set as 192*2  (ACE_Log_Record::MAXLOGMSGL=
>EN * 2).
>
>ssize_t
>ACE_Log_Msg_NT_Event_Log::log (ACE_Log_Record &log_record)
>{
>  // Make a copy of the log text and replace any newlines with
>  // CR-LF. Newline characters on their own do not appear correctly in
>  // the event viewer. We allow for a doubling in the size of the msg
>  // data for the worst case of all newlines.
>  const ACE_TCHAR* src_msg_data =3D log_record.msg_data ();
>  ACE_TCHAR msg_data [ACE_Log_Record::MAXLOGMSGLEN * 2];
>
>  for (size_t i =3D 0, j =3D 0;
>       i < log_record.msg_data_len ();
>       ++i)
>    {
>      if (src_msg_data[i] =3D=3D '\n')    (point where code is crashing , b=
>uffer overflow)
>        {
>          msg_data[j++] =3D '\r';
>          msg_data[j++] =3D '\n';
>        }
>      else
>        msg_data[j++] =3D src_msg_data[i];
>    }
>
>  Some code.....
>
>}
>
>If the log_record.msg_data () size is greater than 192*2 than there is buff=
>er overflow.

Yikes!

>Default msg_data size allocated from heap in the ACE_Log_Record is 192 but =
>it can be increased if the new msg_data set size is larger.
>
>int
>ACE_Log_Record::msg_data (const ACE_TCHAR *data)
>{
>  // ACE_TRACE ("ACE_Log_Record::msg_data");
>  size_t const newlen =3D ACE_OS::strlen (data) + 1;  // Will need room for=
> '\0'
>  if (newlen > this->msg_data_size_)
>    {
>      ACE_TCHAR *new_msg_data =3D 0;
>      ACE_NEW_RETURN (new_msg_data, ACE_TCHAR[newlen], -1);
>      delete [] this->msg_data_;
>      this->msg_data_ =3D new_msg_data;
>      this->msg_data_size_ =3D newlen;
>    }
>  ACE_OS::strcpy (this->msg_data_, data);
>  this->round_up ();
>  return 0;
>}
>
>Let me know what do you think.

It looks to me like we need to do something similar in
ACE_Log_Msg_NT_Event_Log::log (ACE_Log_Record &log_record), i.e.,
(re)allocate msg_data accordingly.  Could you please take a shot at
doing this and let us know how it goes?

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.schmidt@...

------=neXtPaRt_1258625903
Content-Type: text/plain;

===============
DISCLAIMER: The information in this message is confidential and may be legally
privileged. It is intended solely for the addressee. Access to this message by
anyone else is unauthorized. If you are not the intended recipient, any
disclosure, copying, or distribution of the message, or any action or omission
taken by you in reliance on it, is prohibited and may be unlawful. Please
immediately contact the sender if you have received this message in error.
Further, this e-mail may contain viruses and all reasonable precaution to
minimize the risk arising there from is taken by OnMobile. OnMobile is not
liable for any damage sustained by you as a result of any virus in this e-mail.
All applicable virus checks should be carried out by you before opening this
e-mail or any attachment thereto.
Thank you - OnMobile Global Limited.
===============

------=neXtPaRt_1258625903--

_______________________________________________
ace-bugs mailing list
ace-bugs@...
http://list.isis.vanderbilt.edu/mailman/listinfo/ace-bugs

Reply | Forward | Messages in this Topic (11)
#6166 From: schmidt@... (Douglas C. Schmidt)
Date: Wed Nov 18, 2009 2:43 pm
Subject: Re: ACE_Log_Msg_NT_Event_Log not able log a large string 		schmidt@...
Send Email Send Email
  
Hi Gaurav,

>I am aware that using the ACE_Log_Msg_NT_Event_Log without open will not wo=
>rk (sample code). I was only concerned about the logged string size in case=
> of crash.
>After debugging I found out what part of the code is causing the problem. M=
>aximum size of a logged string is set as 192*2  (ACE_Log_Record::MAXLOGMSGL=
>EN * 2).
>
>ssize_t
>ACE_Log_Msg_NT_Event_Log::log (ACE_Log_Record &log_record)
>{
>  // Make a copy of the log text and replace any newlines with
>  // CR-LF. Newline characters on their own do not appear correctly in
>  // the event viewer. We allow for a doubling in the size of the msg
>  // data for the worst case of all newlines.
>  const ACE_TCHAR* src_msg_data =3D log_record.msg_data ();
>  ACE_TCHAR msg_data [ACE_Log_Record::MAXLOGMSGLEN * 2];
>
>  for (size_t i =3D 0, j =3D 0;
>       i < log_record.msg_data_len ();
>       ++i)
>    {
>      if (src_msg_data[i] =3D=3D '\n')    (point where code is crashing , b=
>uffer overflow)
>        {
>          msg_data[j++] =3D '\r';
>          msg_data[j++] =3D '\n';
>        }
>      else
>        msg_data[j++] =3D src_msg_data[i];
>    }
>
>  Some code.....
>
>}
>
>If the log_record.msg_data () size is greater than 192*2 than there is buff=
>er overflow.

Yikes!

>Default msg_data size allocated from heap in the ACE_Log_Record is 192 but =
>it can be increased if the new msg_data set size is larger.
>
>int
>ACE_Log_Record::msg_data (const ACE_TCHAR *data)
>{
>  // ACE_TRACE ("ACE_Log_Record::msg_data");
>  size_t const newlen =3D ACE_OS::strlen (data) + 1;  // Will need room for=
> '\0'
>  if (newlen > this->msg_data_size_)
>    {
>      ACE_TCHAR *new_msg_data =3D 0;
>      ACE_NEW_RETURN (new_msg_data, ACE_TCHAR[newlen], -1);
>      delete [] this->msg_data_;
>      this->msg_data_ =3D new_msg_data;
>      this->msg_data_size_ =3D newlen;
>    }
>  ACE_OS::strcpy (this->msg_data_, data);
>  this->round_up ();
>  return 0;
>}
>
>Let me know what do you think.

It looks to me like we need to do something similar in
ACE_Log_Msg_NT_Event_Log::log (ACE_Log_Record &log_record), i.e.,
(re)allocate msg_data accordingly.  Could you please take a shot at
doing this and let us know how it goes?

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.schmidt@...
_______________________________________________
ace-bugs mailing list
ace-bugs@...
http://list.isis.vanderbilt.edu/mailman/listinfo/ace-bugs

Reply | Forward | Messages in this Topic (11)
#6165 From: Gaurav Kulshreshtha <gaurav.kulshreshtha@...>
Date: Wed Nov 18, 2009 12:13 pm
Subject: Re: ACE_Log_Msg_NT_Event_Log not able log a large string 		gaurav.kulshreshtha@...
Send Email Send Email
 

Hi Aleksandar,

I am aware that using the ACE_Log_Msg_NT_Event_Log without open will not work (sample code). I was only concerned about the logged string size in case of crash.

After debugging I found out what part of the code is causing the problem. Maximum size of a logged string is set as 192*2  (ACE_Log_Record::MAXLOGMSGLEN * 2).

 

ssize_t

ACE_Log_Msg_NT_Event_Log::log (ACE_Log_Record &log_record)

{

  // Make a copy of the log text and replace any newlines with

  // CR-LF. Newline characters on their own do not appear correctly in

  // the event viewer. We allow for a doubling in the size of the msg

  // data for the worst case of all newlines.

  const ACE_TCHAR* src_msg_data = log_record.msg_data ();

  ACE_TCHAR msg_data [ACE_Log_Record::MAXLOGMSGLEN * 2];

 

  for (size_t i = 0, j = 0;

       i < log_record.msg_data_len ();

       ++i)

    {

      if (src_msg_data[i] == '\n')    (point where code is crashing , buffer overflow)

        {

          msg_data[j++] = '\r';

          msg_data[j++] = '\n';

        }

      else

        msg_data[j++] = src_msg_data[i];

    }

 

  Some code…..

 

}

 

If the log_record.msg_data () size is greater than 192*2 than there is buffer overflow.

 

Default msg_data size allocated from heap in the ACE_Log_Record is 192 but it can be increased if the new msg_data set size is larger.

 

int

ACE_Log_Record::msg_data (const ACE_TCHAR *data)

{

  // ACE_TRACE ("ACE_Log_Record::msg_data");

  size_t const newlen = ACE_OS::strlen (data) + 1;  // Will need room for '\0'

  if (newlen > this->msg_data_size_)

    {

      ACE_TCHAR *new_msg_data = 0;

      ACE_NEW_RETURN (new_msg_data, ACE_TCHAR[newlen], -1);

      delete [] this->msg_data_;

      this->msg_data_ = new_msg_data;

      this->msg_data_size_ = newlen;

    }

  ACE_OS::strcpy (this->msg_data_, data);

  this->round_up ();

  return 0;

}

 

Let me know what do you think.

 

Regards,

Gaurav

 

 

From: Aleksandar Vukajlovic [mailto:aleksandar.vukajlovic@...]
Sent: Tuesday, November 17, 2009 6:14 PM
To: Gaurav Kulshreshtha
Cc: ace-bugs@...
Subject: RE: [ace-bugs] ACE_Log_Msg_NT_Event_Log not able log a large string

 

Just as hint, I have tried your sample code with latest ace. Your code sample is bad,  it miss to call open () on log, after opening  it works.

 

Regards

Aleksandar V.

 

From: ace-bugs-bounces@... [mailto:ace-bugs-bounces@...] On Behalf Of Gaurav Kulshreshtha
Sent: Thursday, November 12, 2009 15:06
To: jwillemsen@...; ace-bugs@...
Subject: Re: [ace-bugs] ACE_Log_Msg_NT_Event_Log not able log a large string

 

I am still having the same issue in the latest ace.

 

Sample code attached.

 

Regards,

Gaurav

 

 

 

From: Johnny Willemsen [mailto:jwillemsen@...]
Sent: Wednesday, October 21, 2009 6:57 PM
To: Gaurav Kulshreshtha; ace-bugs@...
Subject: RE: [ace-bugs] ACE_Log_Msg_NT_Event_Log not able log a large string

 

Hi,

 

There have been some bugs fixed when logging large strings, please upgrade to x.7.4

 

Johnny

 

From: ace-bugs-bounces@... [mailto:ace-bugs-bounces@...] On Behalf Of Gaurav Kulshreshtha
Sent: woensdag 21 oktober 2009 10:21
To: ace-bugs@...
Subject: [ace-bugs] ACE_Log_Msg_NT_Event_Log not able log a large string

 

Hi,

I am new to ace and using ace 5.6.6. Before trying to post on this mail I tried to find in the bug-archive whether this problem has already been reported, but I am not able to access bug-archive.

 

ACE_Log_Msg_NT_Event_Log log api crashes when ACE_Log_Record msg_data is set quit large (600 char). Has anybody seen this issue or let me know if this has  been already reported?

 

Regards,

Gaurav

 

Finsoft Ltd. Registered in England and Wales No. 3054588, 16-18 Hatton Garden, London, EC1N 8AT

The information in this E-mail is confidential. If you are not the intended recipient please notify the sender immediately and delete this E-mail without reading, using or disseminating the information contained in it. Although Finsoft Ltd believes this E-mail and any attachments are free of any virus or other defect which may affect a computer, it is the responsibility of the recipient to ensure that it is virus free and Finsoft Ltd does not accept any responsibility for any loss or damage arising in any way from its use.

==============================
DISCLAIMER: The information in this message is confidential and may be legally
privileged. It is intended solely for the addressee. Access to this message by
anyone else is unauthorized. If you are not the intended recipient, any
disclosure, copying, or distribution of the message, or any action or omission
taken by you in reliance on it, is prohibited and may be unlawful. Please
immediately contact the sender if you have received this message in error.
Further, this e-mail may contain viruses and all reasonable precaution to
minimize the risk arising there from is taken by OnMobile. OnMobile is not
liable for any damage sustained by you as a result of any virus in this e-mail.
All applicable virus checks should be carried out by you before opening this
e-mail or any attachment thereto.
Thank you - OnMobile Global Limited.
==============================
_______________________________________________
ace-bugs mailing list
ace-bugs@...
http://list.isis.vanderbilt.edu/mailman/listinfo/ace-bugs

Reply | Forward | Messages in this Topic (11)
#6164 From: Aleksandar Vukajlovic <aleksandar.vukajlovic@...>
Date: Tue Nov 17, 2009 12:44 pm
Subject: Re: ACE_Log_Msg_NT_Event_Log not able log a large string 		aleksandar.vukajlovic@...
Send Email Send Email
 

Just as hint, I have tried your sample code with latest ace. Your code sample is bad,  it miss to call open () on log, after opening  it works.

 

Regards

Aleksandar V.

 

From: ace-bugs-bounces@... [mailto:ace-bugs-bounces@...] On Behalf Of Gaurav Kulshreshtha
Sent: Thursday, November 12, 2009 15:06
To: jwillemsen@...; ace-bugs@...
Subject: Re: [ace-bugs] ACE_Log_Msg_NT_Event_Log not able log a large string

 

I am still having the same issue in the latest ace.

 

Sample code attached.

 

Regards,

Gaurav

 

 

 

From: Johnny Willemsen [mailto:jwillemsen@...]
Sent: Wednesday, October 21, 2009 6:57 PM
To: Gaurav Kulshreshtha; ace-bugs@...
Subject: RE: [ace-bugs] ACE_Log_Msg_NT_Event_Log not able log a large string

 

Hi,

 

There have been some bugs fixed when logging large strings, please upgrade to x.7.4

 

Johnny

 

From: ace-bugs-bounces@... [mailto:ace-bugs-bounces@...] On Behalf Of Gaurav Kulshreshtha
Sent: woensdag 21 oktober 2009 10:21
To: ace-bugs@...
Subject: [ace-bugs] ACE_Log_Msg_NT_Event_Log not able log a large string

 

Hi,

I am new to ace and using ace 5.6.6. Before trying to post on this mail I tried to find in the bug-archive whether this problem has already been reported, but I am not able to access bug-archive.

 

ACE_Log_Msg_NT_Event_Log log api crashes when ACE_Log_Record msg_data is set quit large (600 char). Has anybody seen this issue or let me know if this has  been already reported?

 

Regards,

Gaurav


Finsoft Ltd. Registered in England and Wales No. 3054588, 16-18 Hatton Garden, London, EC1N 8AT

The information in this E-mail is confidential. If you are not the intended recipient please notify the sender immediately and delete this E-mail without reading, using or disseminating the information contained in it. Although Finsoft Ltd believes this E-mail and any attachments are free of any virus or other defect which may affect a computer, it is the responsibility of the recipient to ensure that it is virus free and Finsoft Ltd does not accept any responsibility for any loss or damage arising in any way from its use.
 
_______________________________________________
ace-bugs mailing list
ace-bugs@...
http://list.isis.vanderbilt.edu/mailman/listinfo/ace-bugs

Reply | Forward | Messages in this Topic (11)
#6163 From: "Johnny Willemsen" <jwillemsen@...>
Date: Tue Nov 17, 2009 12:27 pm
Subject: Re: ACE_Log_Msg_NT_Event_Log not able log a large string 		jwillemsen@...
Send Email Send Email
 

Hi,

 

It should be a one button tests like everything under ACE-wrappers/tests, just one simple test that reproduces the bug.

 

Johnny

 

From: Gaurav Kulshreshtha [mailto:gaurav.kulshreshtha@...]
Sent: dinsdag 17 november 2009 13:21
To: jwillemsen@...; ace-bugs@...
Subject: RE: [ace-bugs] ACE_Log_Msg_NT_Event_Log not able log a large string

 

Hi,

Can I prepare a simple test, testing only my failing scenario or does it need to be exhaustive like other tests ?

 

Regards,

Gaurav

 

 

 

From: Johnny Willemsen [mailto:jwillemsen@...]
Sent: Thursday, November 12, 2009 7:38 PM
To: Gaurav Kulshreshtha; ace-bugs@...
Subject: RE: [ace-bugs] ACE_Log_Msg_NT_Event_Log not able log a large string

 

Hi,

 

Can you make a new test, based on an existing test in ACE_wrappers/tests and then report this in bugzilla?

 

Johnny

 

From: Gaurav Kulshreshtha [mailto:gaurav.kulshreshtha@...]
Sent: donderdag 12 november 2009 15:06
To: jwillemsen@...; ace-bugs@...
Subject: RE: [ace-bugs] ACE_Log_Msg_NT_Event_Log not able log a large string

 

I am still having the same issue in the latest ace.

 

Sample code attached.

 

Regards,

Gaurav

 

 

 

From: Johnny Willemsen [mailto:jwillemsen@...]
Sent: Wednesday, October 21, 2009 6:57 PM
To: Gaurav Kulshreshtha; ace-bugs@...
Subject: RE: [ace-bugs] ACE_Log_Msg_NT_Event_Log not able log a large string

 

Hi,

 

There have been some bugs fixed when logging large strings, please upgrade to x.7.4

 

Johnny

 

From: ace-bugs-bounces@... [mailto:ace-bugs-bounces@...] On Behalf Of Gaurav Kulshreshtha
Sent: woensdag 21 oktober 2009 10:21
To: ace-bugs@...
Subject: [ace-bugs] ACE_Log_Msg_NT_Event_Log not able log a large string

 

Hi,

I am new to ace and using ace 5.6.6. Before trying to post on this mail I tried to find in the bug-archive whether this problem has already been reported, but I am not able to access bug-archive.

 

ACE_Log_Msg_NT_Event_Log log api crashes when ACE_Log_Record msg_data is set quit large (600 char). Has anybody seen this issue or let me know if this has  been already reported?

 

Regards,

Gaurav

_______________________________________________
ace-bugs mailing list
ace-bugs@...
http://list.isis.vanderbilt.edu/mailman/listinfo/ace-bugs

Reply | Forward | Messages in this Topic (11)
#6162 From: Gaurav Kulshreshtha <gaurav.kulshreshtha@...>
Date: Tue Nov 17, 2009 12:21 pm
Subject: Re: ACE_Log_Msg_NT_Event_Log not able log a large string 		gaurav.kulshreshtha@...
Send Email Send Email
 

Hi,

Can I prepare a simple test, testing only my failing scenario or does it need to be exhaustive like other tests ?

 

Regards,

Gaurav

 

 

 

From: Johnny Willemsen [mailto:jwillemsen@...]
Sent: Thursday, November 12, 2009 7:38 PM
To: Gaurav Kulshreshtha; ace-bugs@...
Subject: RE: [ace-bugs] ACE_Log_Msg_NT_Event_Log not able log a large string

 

Hi,

 

Can you make a new test, based on an existing test in ACE_wrappers/tests and then report this in bugzilla?

 

Johnny

 

From: Gaurav Kulshreshtha [mailto:gaurav.kulshreshtha@...]
Sent: donderdag 12 november 2009 15:06
To: jwillemsen@...; ace-bugs@...
Subject: RE: [ace-bugs] ACE_Log_Msg_NT_Event_Log not able log a large string

 

I am still having the same issue in the latest ace.

 

Sample code attached.

 

Regards,

Gaurav

 

 

 

From: Johnny Willemsen [mailto:jwillemsen@...]
Sent: Wednesday, October 21, 2009 6:57 PM
To: Gaurav Kulshreshtha; ace-bugs@...
Subject: RE: [ace-bugs] ACE_Log_Msg_NT_Event_Log not able log a large string

 

Hi,

 

There have been some bugs fixed when logging large strings, please upgrade to x.7.4

 

Johnny

 

From: ace-bugs-bounces@... [mailto:ace-bugs-bounces@...] On Behalf Of Gaurav Kulshreshtha
Sent: woensdag 21 oktober 2009 10:21
To: ace-bugs@...
Subject: [ace-bugs] ACE_Log_Msg_NT_Event_Log not able log a large string

 

Hi,

I am new to ace and using ace 5.6.6. Before trying to post on this mail I tried to find in the bug-archive whether this problem has already been reported, but I am not able to access bug-archive.

 

ACE_Log_Msg_NT_Event_Log log api crashes when ACE_Log_Record msg_data is set quit large (600 char). Has anybody seen this issue or let me know if this has  been already reported?

 

Regards,

Gaurav

==============================
DISCLAIMER: The information in this message is confidential and may be legally
privileged. It is intended solely for the addressee. Access to this message by
anyone else is unauthorized. If you are not the intended recipient, any
disclosure, copying, or distribution of the message, or any action or omission
taken by you in reliance on it, is prohibited and may be unlawful. Please
immediately contact the sender if you have received this message in error.
Further, this e-mail may contain viruses and all reasonable precaution to
minimize the risk arising there from is taken by OnMobile. OnMobile is not
liable for any damage sustained by you as a result of any virus in this e-mail.
All applicable virus checks should be carried out by you before opening this
e-mail or any attachment thereto.
Thank you - OnMobile Global Limited.
==============================
_______________________________________________
ace-bugs mailing list
ace-bugs@...
http://list.isis.vanderbilt.edu/mailman/listinfo/ace-bugs

Reply | Forward | Messages in this Topic (11)
#6161 From: "Johnny Willemsen" <jwillemsen@...>
Date: Thu Nov 12, 2009 2:07 pm
Subject: Re: ACE_Log_Msg_NT_Event_Log not able log a large string 		jwillemsen@...
Send Email Send Email
 

Hi,

 

Can you make a new test, based on an existing test in ACE_wrappers/tests and then report this in bugzilla?

 

Johnny

 

From: Gaurav Kulshreshtha [mailto:gaurav.kulshreshtha@...]
Sent: donderdag 12 november 2009 15:06
To: jwillemsen@...; ace-bugs@...
Subject: RE: [ace-bugs] ACE_Log_Msg_NT_Event_Log not able log a large string

 

I am still having the same issue in the latest ace.

 

Sample code attached.

 

Regards,

Gaurav

 

 

 

From: Johnny Willemsen [mailto:jwillemsen@...]
Sent: Wednesday, October 21, 2009 6:57 PM
To: Gaurav Kulshreshtha; ace-bugs@...
Subject: RE: [ace-bugs] ACE_Log_Msg_NT_Event_Log not able log a large string

 

Hi,

 

There have been some bugs fixed when logging large strings, please upgrade to x.7.4

 

Johnny

 

From: ace-bugs-bounces@... [mailto:ace-bugs-bounces@...] On Behalf Of Gaurav Kulshreshtha
Sent: woensdag 21 oktober 2009 10:21
To: ace-bugs@...
Subject: [ace-bugs] ACE_Log_Msg_NT_Event_Log not able log a large string

 

Hi,

I am new to ace and using ace 5.6.6. Before trying to post on this mail I tried to find in the bug-archive whether this problem has already been reported, but I am not able to access bug-archive.

 

ACE_Log_Msg_NT_Event_Log log api crashes when ACE_Log_Record msg_data is set quit large (600 char). Has anybody seen this issue or let me know if this has  been already reported?

 

Regards,

Gaurav

_______________________________________________
ace-bugs mailing list
ace-bugs@...
http://list.isis.vanderbilt.edu/mailman/listinfo/ace-bugs

Reply | Forward | Messages in this Topic (11)
#6160 From: Gaurav Kulshreshtha <gaurav.kulshreshtha@...>
Date: Thu Nov 12, 2009 2:06 pm
Subject: Re: ACE_Log_Msg_NT_Event_Log not able log a large string 		gaurav.kulshreshtha@...
Send Email Send Email
 

I am still having the same issue in the latest ace.

 

Sample code attached.

 

Regards,

Gaurav

 

 

 

From: Johnny Willemsen [mailto:jwillemsen@...]
Sent: Wednesday, October 21, 2009 6:57 PM
To: Gaurav Kulshreshtha; ace-bugs@...
Subject: RE: [ace-bugs] ACE_Log_Msg_NT_Event_Log not able log a large string

 

Hi,

 

There have been some bugs fixed when logging large strings, please upgrade to x.7.4

 

Johnny

 

From: ace-bugs-bounces@... [mailto:ace-bugs-bounces@...] On Behalf Of Gaurav Kulshreshtha
Sent: woensdag 21 oktober 2009 10:21
To: ace-bugs@...
Subject: [ace-bugs] ACE_Log_Msg_NT_Event_Log not able log a large string

 

Hi,

I am new to ace and using ace 5.6.6. Before trying to post on this mail I tried to find in the bug-archive whether this problem has already been reported, but I am not able to access bug-archive.

 

ACE_Log_Msg_NT_Event_Log log api crashes when ACE_Log_Record msg_data is set quit large (600 char). Has anybody seen this issue or let me know if this has  been already reported?

 

Regards,

Gaurav

==============================
DISCLAIMER: The information in this message is confidential and may be legally
privileged. It is intended solely for the addressee. Access to this message by
anyone else is unauthorized. If you are not the intended recipient, any
disclosure, copying, or distribution of the message, or any action or omission
taken by you in reliance on it, is prohibited and may be unlawful. Please
immediately contact the sender if you have received this message in error.
Further, this e-mail may contain viruses and all reasonable precaution to
minimize the risk arising there from is taken by OnMobile. OnMobile is not
liable for any damage sustained by you as a result of any virus in this e-mail.
All applicable virus checks should be carried out by you before opening this
e-mail or any attachment thereto.
Thank you - OnMobile Global Limited.
==============================
_______________________________________________
ace-bugs mailing list
ace-bugs@...
http://list.isis.vanderbilt.edu/mailman/listinfo/ace-bugs

Reply | Forward | Messages in this Topic (11)
#6159 From: "Douglas C. Schmidt" <schmidt@...>
Date: Thu Oct 22, 2009 9:14 pm
Subject: Re: ACE_Pipe::recv doxygen documentation error 		schmidt@...
Send Email Send Email
  
[Eric, there's a request for you below.]

Hi Matthew,

    Thanks for using the PRF!

>     ACE VERSION: 5.6.9
>
>     HOST MACHINE and OPERATING SYSTEM:
>       N/A
>
>     TARGET MACHINE and OPERATING SYSTEM, if different from HOST:
>     COMPILER NAME AND VERSION (AND PATCHLEVEL):
>       N/A
>
>     THE $ACE_ROOT/ace/config.h FILE:
>       N/A
>
>     THE $ACE_ROOT/include/makeinclude/platform_macros.GNU FILE:
>       N/A
>
>     CONTENTS OF $ACE_ROOT/bin/MakeProjectCreator/config/default.features
>     (used by MPC when you generate your own makefiles):
>       N/A
>
>     AREA/CLASS/EXAMPLE AFFECTED:
>       ACE_Pipe
>
>     DOES THE PROBLEM AFFECT:
>         COMPILATION?
>           No.
>         LINKING?
>           No.
>         EXECUTION?
>           No.
>         OTHER (please specify)?
>           Documentation
>
>     SYNOPSIS:
>       The doxygen documentation for the varargs recv method on the ACE_Pipe
class does not make sense.
>
>     DESCRIPTION:
>
> The documentations states:
>     This is an interface to ::readv, that doesn't use the struct
>     iovec explicitly.  The ... can be passed as an arbitrary number
>     of (char *ptr, int len) tuples.  However, the count N is the
>     *total* number of trailing arguments, *not* a couple of the
>     number of tuple pairs!
>
> The last few words should be corrected to:
>     "*not* the number of tuples!"
>
>
>     REPEAT BY:
>       N/A
>
>     SAMPLE FIX/WORKAROUND:
>
> Apply this patch:
>
> Index: Pipe.h
> ===================================================================
> --- Pipe.h      (revision 23983)
> +++ Pipe.h      (working copy)
> @@ -122,8 +122,7 @@
>     * This is an interface to ::readv, that doesn't use the struct
>     * iovec explicitly.  The ... can be passed as an arbitrary number
>     * of (char *ptr, int len) tuples.  However, the count N is the
> -   * *total* number of trailing arguments, *not* a couple of the
> -   * number of tuple pairs!
> +   * *total* number of trailing arguments, *not* the number of tuples!
>     */
>    ssize_t recv (size_t n, ...) const;

I've fixed this to say:

   /**
    * This is an interface to ::readv, that doesn't use the struct
    * iovec explicitly.  The ... can be passed as an arbitrary number
    * of (char *ptr, int len) tuples.  However, the count N is the
    * *total* number of trailing arguments, *not* a count of the
    * number of tuple pairs!
    */

Does that make more sense?

> I attempted to enter this bug report into the bug tracking database as
> instructed, but the permissions on my bugzilla account do not appear
> to allow me to submit bug reports.

Eric, can you please allow Matthew to submit bug reports via bugzilla?

Thanks,

         Doug
_______________________________________________
ace-bugs mailing list
ace-bugs@...
http://list.isis.vanderbilt.edu/mailman/listinfo/ace-bugs

Reply | Forward | Messages in this Topic (2)
#6158 From: "Matthew P. Carter" <r_q_einstein-acetaobugs@...>
Date: Thu Oct 22, 2009 5:38 pm
Subject: ACE_Pipe::recv doxygen documentation error 		r_q_einstein-acetaobugs@...
Send Email Send Email
  
ACE VERSION: 5.6.9

     HOST MACHINE and OPERATING SYSTEM:
       N/A

     TARGET MACHINE and OPERATING SYSTEM, if different from HOST:
     COMPILER NAME AND VERSION (AND PATCHLEVEL):
       N/A

     THE $ACE_ROOT/ace/config.h FILE:
       N/A

     THE $ACE_ROOT/include/makeinclude/platform_macros.GNU FILE:
       N/A

     CONTENTS OF $ACE_ROOT/bin/MakeProjectCreator/config/default.features
     (used by MPC when you generate your own makefiles):
       N/A

     AREA/CLASS/EXAMPLE AFFECTED:
       ACE_Pipe

     DOES THE PROBLEM AFFECT:
         COMPILATION?
           No.
         LINKING?
           No.
         EXECUTION?
           No.
         OTHER (please specify)?
           Documentation

     SYNOPSIS:
       The doxygen documentation for the varargs recv method on the ACE_Pipe
class does not make sense.

     DESCRIPTION:

The documentations states:
     This is an interface to ::readv, that doesn't use the struct
     iovec explicitly.  The ... can be passed as an arbitrary number
     of (char *ptr, int len) tuples.  However, the count N is the
     *total* number of trailing arguments, *not* a couple of the
     number of tuple pairs!

The last few words should be corrected to:
     "*not* the number of tuples!"


     REPEAT BY:
       N/A

     SAMPLE FIX/WORKAROUND:

Apply this patch:

Index: Pipe.h
===================================================================
--- Pipe.h      (revision 23983)
+++ Pipe.h      (working copy)
@@ -122,8 +122,7 @@
     * This is an interface to ::readv, that doesn't use the struct
     * iovec explicitly.  The ... can be passed as an arbitrary number
     * of (char *ptr, int len) tuples.  However, the count N is the
-   * *total* number of trailing arguments, *not* a couple of the
-   * number of tuple pairs!
+   * *total* number of trailing arguments, *not* the number of tuples!
     */
    ssize_t recv (size_t n, ...) const;


I attempted to enter this bug report into the bug tracking database as
instructed, but the permissions on my bugzilla account do not appear to allow me
to submit bug reports.
_______________________________________________
ace-bugs mailing list
ace-bugs@...
http://list.isis.vanderbilt.edu/mailman/listinfo/ace-bugs

Reply | Forward | Messages in this Topic (2)
#6157 From: "Johnny Willemsen" <jwillemsen@...>
Date: Wed Oct 21, 2009 1:26 pm
Subject: Re: ACE_Log_Msg_NT_Event_Log not able log a large string 		jwillemsen@...
Send Email Send Email
 

Hi,

 

There have been some bugs fixed when logging large strings, please upgrade to x.7.4

 

Johnny

 

From: ace-bugs-bounces@... [mailto:ace-bugs-bounces@...] On Behalf Of Gaurav Kulshreshtha
Sent: woensdag 21 oktober 2009 10:21
To: ace-bugs@...
Subject: [ace-bugs] ACE_Log_Msg_NT_Event_Log not able log a large string

 

Hi,

I am new to ace and using ace 5.6.6. Before trying to post on this mail I tried to find in the bug-archive whether this problem has already been reported, but I am not able to access bug-archive.

 

ACE_Log_Msg_NT_Event_Log log api crashes when ACE_Log_Record msg_data is set quit large (600 char). Has anybody seen this issue or let me know if this has  been already reported?

 

Regards,

Gaurav

_______________________________________________
ace-bugs mailing list
ace-bugs@...
http://list.isis.vanderbilt.edu/mailman/listinfo/ace-bugs

Reply | Forward | Messages in this Topic (11)
#6156 From: Gaurav Kulshreshtha <gaurav.kulshreshtha@...>
Date: Wed Oct 21, 2009 8:21 am
Subject: ACE_Log_Msg_NT_Event_Log not able log a large string 		gaurav.kulshreshtha@...
Send Email Send Email
 

Hi,

I am new to ace and using ace 5.6.6. Before trying to post on this mail I tried to find in the bug-archive whether this problem has already been reported, but I am not able to access bug-archive.

 

ACE_Log_Msg_NT_Event_Log log api crashes when ACE_Log_Record msg_data is set quit large (600 char). Has anybody seen this issue or let me know if this has  been already reported?

 

Regards,

Gaurav

==============================
DISCLAIMER: The information in this message is confidential and may be legally
privileged. It is intended solely for the addressee. Access to this message by
anyone else is unauthorized. If you are not the intended recipient, any
disclosure, copying, or distribution of the message, or any action or omission
taken by you in reliance on it, is prohibited and may be unlawful. Please
immediately contact the sender if you have received this message in error.
Further, this e-mail may contain viruses and all reasonable precaution to
minimize the risk arising there from is taken by OnMobile. OnMobile is not
liable for any damage sustained by you as a result of any virus in this e-mail.
All applicable virus checks should be carried out by you before opening this
e-mail or any attachment thereto.
Thank you - OnMobile Global Limited.
==============================
_______________________________________________
ace-bugs mailing list
ace-bugs@...
http://list.isis.vanderbilt.edu/mailman/listinfo/ace-bugs

Reply | Forward | Messages in this Topic (11)
#6155 From: "Johnny Willemsen" <jwillemsen@...>
Date: Fri Oct 16, 2009 12:11 pm
Subject: Re: Bug #3714 in bugzilla 		jwillemsen@...
Send Email Send Email
  
Hi,

I have just given you permission to post to bugzilla.

Johnny

> Hi there!
>
> I'd like to watch and possibly to help to fix the bug #3714 (high cpu
> usage of Dev_Poll_Reactor). But the policy prevents me to comment on
> it. How else can I get involved?
>
> Anatoli Sakhnik
> _______________________________________________
> ace-bugs mailing list
> ace-bugs@...
> http://list.isis.vanderbilt.edu/mailman/listinfo/ace-bugs

_______________________________________________
ace-bugs mailing list
ace-bugs@...
http://list.isis.vanderbilt.edu/mailman/listinfo/ace-bugs

Reply | Forward | Messages in this Topic (2)
#6154 From: Anatoli Sakhnik <sakhnik@...>
Date: Fri Oct 16, 2009 6:50 am
Subject: Bug #3714 in bugzilla 		sakhnik@...
Send Email Send Email
  
Hi there!

I'd like to watch and possibly to help to fix the bug #3714 (high cpu
usage of Dev_Poll_Reactor). But the policy prevents me to comment on
it. How else can I get involved?

Anatoli Sakhnik
_______________________________________________
ace-bugs mailing list
ace-bugs@...
http://list.isis.vanderbilt.edu/mailman/listinfo/ace-bugs

Reply | Forward | Messages in this Topic (2)
#6153 From: "Johnny Willemsen" <jwillemsen@...>
Date: Wed Oct 14, 2009 7:19 am
Subject: ACE+TAO x.7.4 rpms available from opensuse build service 		jwillemsen@...
Send Email Send Email
  
Hi all,

The ACE+TAO x.7.4 rpms for are available from the opensuse build service at
http://software.opensuse.org/search

We are currently searching for funding to add debian/ubuntu package support
to the open source distribution. If you are interested in funding this work
please contact me.

Regards,

Johnny Willemsen
Remedy IT
http://www.theaceorb.nl

_______________________________________________
ace-bugs mailing list
ace-bugs@...
http://list.isis.vanderbilt.edu/mailman/listinfo/ace-bugs

Reply | Forward | Messages in this Topic (1)
#6152 From: "Johnny Willemsen" <jwillemsen@...>
Date: Tue Oct 13, 2009 5:31 pm
Subject: Re: Warnings in linking of ace on VxWorks 		jwillemsen@...
Send Email Send Email
 

Hi,

 

Thanks for using the PRF form. We as Remedy IT have done the VxWorks 6.6 port but we have focused mainly on gcc.  We would recommend you to upgrade to vxworks 6.7 and ACE/TAO x.7.4

 

Regards,

 

 

Johnny Willemsen

Remedy IT

Postbus 101 - 2650 AC  Berkel en Rodenrijs

Melkrijder 11 - 3861 SG Nijkerk

The Netherlands

www.theaceorb.nl / www.remedy.nl 

 

*** Integrated compile and test statistics see http://scoreboard.theaceorb.nl **

*** Commercial service and support for ACE/TAO/CIAO             ***

*** Get your free TAO Programmers Guide copy from http://www.theaceorb.nl ***

 

 

 

From: ace-bugs-bounces@... [mailto:ace-bugs-bounces@...] On Behalf Of Sharon Mizrahi
Sent: dinsdag 13 oktober 2009 16:24
To: ace-bugs@...
Subject: [ace-bugs] Warnings in linking of ace on VxWorks

 

ACE VERSION:

5.6.5

 

HOST MACHINE and OPERATING SYSTEM:

Intel Pentium 4, Windows XP Professional.

 

TARGET MACHINE and OPERATING SYSTEM:

pentium4diab, VxWorks 6.6

 

COMPILER NAME and VERSION:

Wind River Compiler 5.6

 

THE ace/config.h FILE:

The config.h file has only one line: #include "ace/config-vxworks6.6.h"

 

AREA/CLASS/EXAMPLE AFFECTED:

Warnings in linking of ace (only ace is affected).

 

SYNOPSIS:

Warnings in linking of ace.

 

DESCRIPTION:

When linking ace there are a lot of warnings regarding to redeclarations. Most of the warnings indicate redeclaration with os.o.

Example of linker output:

Warning: Redeclaration of ace_cleanup_destroyer

Defined in ace/debug/objects/ace/cleanup.o

and ace/debug/objects/ace/os.o

 

 

_______________________________________________
ace-bugs mailing list
ace-bugs@...
http://list.isis.vanderbilt.edu/mailman/listinfo/ace-bugs

Reply | Forward | Messages in this Topic (3)
#6151 From: "Douglas C. Schmidt" <schmidt@...>
Date: Tue Oct 13, 2009 2:27 pm
Subject: Re: Warnings in linking of ace on VxWorks 		schmidt@...
Send Email Send Email
  
Hi Sharon,

    Thanks for using the PRF!

> ACE VERSION:
> 5.6.5

Please upgrade to ACE+TAO+CIAO x.7.4 (i.e., ACE 5.7.4, TAO 1.7.4, and CIAO
0.7.4), which you can download from

http://download.dre.vanderbilt.edu

under the heading: "Latest Micro Release Kit."

The DOC groups at Washington University, UC Irvine, and Vanderbilt
University only provide "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.

Thanks,

         Doug


> HOST MACHINE and OPERATING SYSTEM:
> Intel Pentium 4, Windows XP Professional.
>  
> TARGET MACHINE and OPERATING SYSTEM:
> pentium4diab, VxWorks 6.6
>  
> COMPILER NAME and VERSION:
> Wind River Compiler 5.6
>  
> THE ace/config.h FILE:
> The config.h file has only one line: #include "ace/
> config-vxworks6.6.h"
>  
> AREA/CLASS/EXAMPLE AFFECTED:
> Warnings in linking of ace (only ace is affected).
>  
> SYNOPSIS:
> Warnings in linking of ace.
>  
> DESCRIPTION:
> When linking ace there are a lot of warnings regarding to
> redeclarations. Most of the warnings indicate redeclaration
> with os.o.
> Example of linker output:
> Warning: Redeclaration of ace_cleanup_destroyer
> Defined in ace/debug/objects/ace/cleanup.o
> and ace/debug/objects/ace/os.o
>  
>  
>
> _______________________________________________
> ace-bugs mailing list
> ace-bugs@...
> http://list.isis.vanderbilt.edu/mailman/listinfo/ace-bugs
_______________________________________________
ace-bugs mailing list
ace-bugs@...
http://list.isis.vanderbilt.edu/mailman/listinfo/ace-bugs

Reply | Forward | Messages in this Topic (3)
#6150 From: Sharon Mizrahi <sharon.mizrahi@...>
Date: Tue Oct 13, 2009 2:24 pm
Subject: Warnings in linking of ace on VxWorks 		sharon.mizrahi@...
Send Email Send Email
 
ACE VERSION:
5.6.5
 
HOST MACHINE and OPERATING SYSTEM:
Intel Pentium 4, Windows XP Professional.
 
TARGET MACHINE and OPERATING SYSTEM:
pentium4diab, VxWorks 6.6
 
COMPILER NAME and VERSION:
Wind River Compiler 5.6
 
THE ace/config.h FILE:
The config.h file has only one line: #include "ace/config-vxworks6.6.h"
 
AREA/CLASS/EXAMPLE AFFECTED:
Warnings in linking of ace (only ace is affected).
 
SYNOPSIS:
Warnings in linking of ace.
 
DESCRIPTION:
When linking ace there are a lot of warnings regarding to redeclarations. Most of the warnings indicate redeclaration with os.o.
Example of linker output:
Warning: Redeclaration of ace_cleanup_destroyer
Defined in ace/debug/objects/ace/cleanup.o
and ace/debug/objects/ace/os.o
 
 
_______________________________________________
ace-bugs mailing list
ace-bugs@...
http://list.isis.vanderbilt.edu/mailman/listinfo/ace-bugs

Reply | Forward | Messages in this Topic (3)
#6149 From: "Johnny Willemsen" <jwillemsen@...>
Date: Tue Oct 13, 2009 6:30 am
Subject: ACE+TAO+CIAO x.7.4 available for download 		jwillemsen@...
Send Email Send Email
  
Hi,

Once again, thanks to the efforts of many developers, testers, and
users, we are pleased to announce the latest ACE+TAO+CIAO x.7.4
micro release, which is available from the usual download location at:

http://download.dre.vanderbilt.edu/

under the heading "Latest Micro Release kit."

This release contains major CIAO changes and some small changes to ACE
and TAO for all the work done in CIAO.

The doxygen documentation for this release is also available. In addition
to the packages combined of sources and generate makefiles, this release
provides source-only packages for developers who use MPC to generate their
own makefiles.

We encourage you to download the new release, use it with your
applications, and let us know if you encounter any problems. Please
use the:

$ACE_ROOT/PROBLEM-REPORT-FORM
$TAO_ROOT/PROBLEM-REPORT-FORM
$CIAO_ROOT/PROBLEM-REPORT-FORM

so that we have the proper version/platform/compiler/options you're
using to report problems. We also request that you take a look at:

$TAO_ROOT/docs/releasenotes/

for the status of various ongoing projects at the DOC groups of WashU,
UCI, and Vanderbilt to move ACE+TAO+CIAO forward.  Overviews of our
recent progress and upcoming plans are available at:

$ACE_ROOT/NEWS
$TAO_ROOT/NEWS
$CIAO_ROOT/NEWS

The overall success rates for the test results gathered from all our
daily builds is 98% for the ACE tests and 94% for the TAO tests.
Please see:

http://www.dre.vanderbilt.edu/scoreboard/

for a summary of these tests. As always, we appreciate your help in
resolving any remaining problems. Please see:

ACE_ROOT/docs/ACE-bug-process.html

for an overview of our bug fixing policies.  Moreover, please see

http://www.dre.vanderbilt.edu/support.html

for information commercial support services available from various
companies.

The following is a list of key changes since the last micro
release. Please refer to the corresponding ChangeLog files, NEWS files
or Bugzilla entries for more details on the problem and the nature of
fixes applied.

==============
Changes to ACE
==============

. ACE_CDR::consolidate now returns an int, 0 is ok, -1 is failure

. Fixed a bug in the realclean feature of the GNU makefiles

. Improved Sun Studio for Linux support

. Improved OpenBSD support

==============
Changes to TAO
==============

. Initial support for IDL3+ in the TAO_IDL compiler front end.
   IDL3+ is an extension to IDL3 driven by the DDS4CCM draft
   standard. IDL3+ adds a porttype which is a logical grouping
   of CCM ports and a concept of templates (like C++)

. Changed behavior of -Glem and -Glfa

. Ported a large set of TAO tests to the new test framework

. Added a capability to throw BAD_PARAM exception in case
   there is an attempt to access sequence elements above
   sequence length. By default this capability is turned on
   in debug builds with defining TAO_CHECKED_SEQUENCE_INDEXING.
   BAD_PARAM exception is also thrown in case a new sequence
   length for bounded sequence is greater than the bound
   defined in IDL.

===============
Changes to CIAO
===============

. Added second prototype of DDS4CCM that uses the RTI
   CORBA Compatibility kit and a monolithic connector

. Extended AMI4CCM prototype

. Update all examples and tests for the changes in the -Glem
   TAO_IDL option.  The behavior of this option has changed
   dramatically, and will require that most user applications be
   ported.  Previously, -Glem would cause the IDL compiler to generate
   a E.idl file containing local executor mapping for all interfaces
   provided as ports by any components in the main translation unit.
   Therefore, files with interfaces, but no components defined will
   have empty E.idl files generated.  Similarly, a file with no
   interfaces defined, but with components defined would generate LEM
   interfaces for interfaces provided by that component but not local
   to the file in question.  While this behavior simplified a
   rudimentary use case where interfaces would be provided by only one
   component, more complicated use cases were much more difficult to
   achieve.

   The new behavior causes the IDL compiler to generate LEM IDL for all
   interfaces within a given translation unit, regardless of whether or
   not they are provided as ports by a component in the same
   translation unit.  Furthermore, if a component provides an interface
   that is not defined with the translation unit of that component, it
   is required that the user provide a #include directive to the
   appropriate E.idl file which contains the required LEM interface for
   the interfaces provided as facets.

   This new behavior is similar to the former behavior of -Glfa, and as
   such the behavior of -Glfa has been changed to attempt to be
   reflective of the old behavior of -Glem, and may be used as a
   stopgap backwards compatibility measure.


. In idl3_to_idl2 tool, replaced manual designation of IDL2-only
   files and resulting generated include of undecorated filename
   (using -x <filename> option) with a mechanism that does it
   automatically. The -x option has been eliminated.

=====================
Bugzilla Issues Fixed
=====================

0 ACE bugs fixed:

3 TAO bugs fixed:
3340 TAO_OutStream uses both fixed sized ACE_CDR and C++ types in overloads
3743 -Se option doesn't work when idl files includes orb.idl
3746 Bounded sequences need more checks for length value is lower than MAX

1 CIAO bugs fixed:
3011 Generated entrypoint names do not match those generated by the CIDL
comp

0 MPC bugs fixed:

_______________________________________________
ace-bugs mailing list
ace-bugs@...
http://list.isis.vanderbilt.edu/mailman/listinfo/ace-bugs

Reply | Forward | Messages in this Topic (1)
#6148 From: Mario Chacon <the.masch@...>
Date: Tue Oct 13, 2009 2:30 am
Subject: Error during compilation ACE-5.4.4 + TAO-1.4.4 		the.masch@...
Send Email Send Email
 
Hello,
I'm trying to compile ACE-5.4.4+TAO-1.4.4 and I got an error while I trying to compile it:

/home/mchacon/nextgen/extra/ACE_wrappers/ace/os_include/os_stropts.h:64:28: error: stropts.h: No such file or directory

I use Fedora 11 with gcc 4.4.1 and I was searching in google and I found that there are some is issue about strems buffer in Linux, please take a look these links:



Is there any workaround to fix it? I have the header in Fedora Core 3, but I trying to make it work in Fedora 11, Is it possible?


Thanks and Regards!
Salu2...
masch...
_______________________________________________
ace-bugs mailing list
ace-bugs@...
http://list.isis.vanderbilt.edu/mailman/listinfo/ace-bugs

Reply | Forward | Messages in this Topic (2)
#6147 From: "Douglas C. Schmidt" <schmidt@...>
Date: Tue Oct 13, 2009 2:53 am
Subject: Re: Error during compilation ACE-5.4.4 + TAO-1.4.4 		schmidt@...
Send Email Send Email
  
Hi Mario,

> I'm trying to compile ACE-5.4.4+TAO-1.4.4 and I got an error while I trying to
compile it:

You are using a very old version of ACE+TAO.  Please upgrade to
ACE+TAO+CIAO x.7.3 (i.e., ACE 5.7.3, TAO 1.7.3, and CIAO 0.7.3), which
you can download from

http://download.dre.vanderbilt.edu

under the heading: "Latest Micro Release Kit."

The DOC groups at Washington University, UC Irvine, and Vanderbilt
University only provide "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.

Thanks,

         Doug


> /home/mchacon/nextgen/extra/ACE_wrappers/ace/os_include/os_stropts.h:64:28:
error: stropts.h: No such file or directory
>
> I use Fedora 11 with gcc 4.4.1 and I was searching in google and I found that
there are some is issue about strems buffer
> in Linux, please take a look these links:
>
>
http://www.archivum.info/comp.soft-sys.ace/2008-04/00069/Re:_[tao-users]_PRF:_Au\
tobuild_on_Fedora_Rawhide_(GCC_4.3.0)
> _is_a_no-go
>
> https://bugzilla.redhat.com/show_bug.cgi?id=439403
>
> Is there any workaround to fix it? I have the header in Fedora Core 3, but I
trying to make it work in Fedora 11, Is it
> possible?
>
> Thanks and Regards!
> Salu2...
> masch...
>
> _______________________________________________
> ace-bugs mailing list
> ace-bugs@...
> http://list.isis.vanderbilt.edu/mailman/listinfo/ace-bugs
_______________________________________________
ace-bugs mailing list
ace-bugs@...
http://list.isis.vanderbilt.edu/mailman/listinfo/ace-bugs

Reply | Forward | Messages in this Topic (2)
#6146 From: Breno Carneiro Pinheiro <brenodee@...>
Date: Mon Oct 12, 2009 2:33 pm
Subject: Re: configure error during cross compiling 		brenodee@...
Send Email Send Email
 
Hi, sorry for my insistence about this but I couldn't realize where it's said that I'm cross-compiling. I mean, I have to create a configuration file $ACE_ROOT/ace/config.h with  #include "ace/config-linux.h" line on it. As I have an armv5te-angstrom-linux-gnueabi on my system, can I use this config.h file already available? How to specify that I'm building for another platform?

Thanks again,

Breno

2009/10/12 Douglas C. Schmidt <schmidt@...>

Hi Breno,

> Thanks for your help.. What do you mean with traditional way?

Please see

ACE_ROOT/ACE-INSTALL.html#unix_traditional

for instructions on using the "traditional" configuration.

Thanks,

       Doug




--
Breno Carneiro Pinheiro
_______________________________________________
ace-bugs mailing list
ace-bugs@...
http://list.isis.vanderbilt.edu/mailman/listinfo/ace-bugs

Reply | Forward | Messages in this Topic (5)
#6145 From: "Douglas C. Schmidt" <schmidt@...>
Date: Mon Oct 12, 2009 2:02 pm
Subject: Re: configure error during cross compiling 		schmidt@...
Send Email Send Email
  
Hi Breno,

> Thanks for your help.. What do you mean with traditional way?

Please see

ACE_ROOT/ACE-INSTALL.html#unix_traditional

for instructions on using the "traditional" configuration.

Thanks,

         Doug

_______________________________________________
ace-bugs mailing list
ace-bugs@...
http://list.isis.vanderbilt.edu/mailman/listinfo/ace-bugs

Reply | Forward | Messages in this Topic (5)
#6144 From: Breno Carneiro Pinheiro <brenodee@...>
Date: Mon Oct 12, 2009 1:58 pm
Subject: Re: configure error during cross compiling 		brenodee@...
Send Email Send Email
 
Thanks for your help.. What do you mean with traditional way? It's supposed to get an make file after configure steps, isn't? Then I can do make && make install. am I wrong?

Thanks again,

Breno

2009/10/12 Johnny Willemsen <jwillemsen@...>

Hi,

 

Use the traditional way of compilation, cross compilation with configure is not support

 

Johnny

 

 

ACE VERSION: 5.7.3



    HOST MACHINE and OPERATING SYSTEM:

       i686-pc-linux



    TARGET MACHINE and OPERATING SYSTEM   

        arm-angstrom-linux-gnueabi

        arm-angstrom-linux-gnueabi-gcc




        gcc-cross-4.1.2-r10

        

    THE $ACE_ROOT/ace/config.h



    THE $ACE_ROOT/include/makeinclude/platform_macros.GNU FILE 



    BUILD METHOD USED:

     mkdir build

     cd build/

     ../configure CXX=path-to-crossbin/arm-angstrom-linux-gnueabi-g++ CC=path-to-crossbin/arm-angstrom-linux-gnueabi-gcc






    CONTENTS OF $ACE_ROOT/bin/MakeProjectCreator/config/default.features

    (used by MPC when you generate your own makefiles):



    AREA/CLASS/EXAMPLE AFFECTED:





    DOES THE PROBLEM AFFECT:

        configuring process error








    SYNOPSIS:

     Message returned:



configure:3630: /home/breno/gumstix/gumstix-oe/tmp/cross/bin/arm-angstrom-linux-gnueabi-g++ -c -g -O2  conftest.cc >&5

conftest.cc: In function 'int main()':




conftest.cc:13: error: 'exit' was not declared in this scope

configure:3636: $? = 1

configure: failed program was:

| /* confdefs.h.  */



configure:3920: /home/breno/gumstix/gumstix-oe/tmp/cross/bin/arm-angstrom-linux-gnueabi-g++ -E  conftest.cc




conftest.cc:12:28: error: ac_nonexistent.h: No such file or directory

configure:3926: $? = 1

configure: failed program was:

| /* confdefs.h.  */

|

| #define PACKAGE_NAME "ACE"



configure:4247: /home/breno/gumstix/gumstix-oe/tmp/cross/bin/arm-angstrom-linux-gnueabi-g++ -o conftest -g -O2   conftest.cc -lfl   >&5




/home/breno/gumstix/gumstix-oe/tmp/cross/lib/gcc/arm-angstrom-linux-gnueabi/4.1.2/../../../../arm-angstrom-linux-gnueabi/bin/ld: cannot find -lfl

collect2: ld returned 1 exit status

configure:4253: $? = 1

configure: failed program was:




| /* confdefs.h.  */





    DESCRIPTION:

    The messages returned shown on synopsis was got during configure process. I couldn't so run make.I decide to attach the log file.



    REPEAT BY:








    SAMPLE FIX/WORKAROUND:


Thanks for any help,
--
Breno Carneiro Pinheiro




--
Breno Carneiro Pinheiro
_______________________________________________
ace-bugs mailing list
ace-bugs@...
http://list.isis.vanderbilt.edu/mailman/listinfo/ace-bugs

Reply | Forward | Messages in this Topic (5)
#6143 From: "Johnny Willemsen" <jwillemsen@...>
Date: Mon Oct 12, 2009 1:52 pm
Subject: Re: configure error during cross compiling 		jwillemsen@...
Send Email Send Email
 

Hi,

 

Use the traditional way of compilation, cross compilation with configure is not support

 

Johnny

 

 

ACE VERSION: 5.7.3



    HOST MACHINE and OPERATING SYSTEM:

       i686-pc-linux



    TARGET MACHINE and OPERATING SYSTEM   

        arm-angstrom-linux-gnueabi

        arm-angstrom-linux-gnueabi-gcc




        gcc-cross-4.1.2-r10

        

    THE $ACE_ROOT/ace/config.h



    THE $ACE_ROOT/include/makeinclude/platform_macros.GNU FILE 



    BUILD METHOD USED:

     mkdir build

     cd build/

     ../configure CXX=path-to-crossbin/arm-angstrom-linux-gnueabi-g++ CC=path-to-crossbin/arm-angstrom-linux-gnueabi-gcc






    CONTENTS OF $ACE_ROOT/bin/MakeProjectCreator/config/default.features

    (used by MPC when you generate your own makefiles):



    AREA/CLASS/EXAMPLE AFFECTED:





    DOES THE PROBLEM AFFECT:

        configuring process error








    SYNOPSIS:

     Message returned:



configure:3630: /home/breno/gumstix/gumstix-oe/tmp/cross/bin/arm-angstrom-linux-gnueabi-g++ -c -g -O2  conftest.cc >&5

conftest.cc: In function 'int main()':




conftest.cc:13: error: 'exit' was not declared in this scope

configure:3636: $? = 1

configure: failed program was:

| /* confdefs.h.  */



configure:3920: /home/breno/gumstix/gumstix-oe/tmp/cross/bin/arm-angstrom-linux-gnueabi-g++ -E  conftest.cc




conftest.cc:12:28: error: ac_nonexistent.h: No such file or directory

configure:3926: $? = 1

configure: failed program was:

| /* confdefs.h.  */

|

| #define PACKAGE_NAME "ACE"



configure:4247: /home/breno/gumstix/gumstix-oe/tmp/cross/bin/arm-angstrom-linux-gnueabi-g++ -o conftest -g -O2   conftest.cc -lfl   >&5




/home/breno/gumstix/gumstix-oe/tmp/cross/lib/gcc/arm-angstrom-linux-gnueabi/4.1.2/../../../../arm-angstrom-linux-gnueabi/bin/ld: cannot find -lfl

collect2: ld returned 1 exit status

configure:4253: $? = 1

configure: failed program was:




| /* confdefs.h.  */





    DESCRIPTION:

    The messages returned shown on synopsis was got during configure process. I couldn't so run make.I decide to attach the log file.



    REPEAT BY:








    SAMPLE FIX/WORKAROUND:


Thanks for any help,
--
Breno Carneiro Pinheiro

_______________________________________________
ace-bugs mailing list
ace-bugs@...
http://list.isis.vanderbilt.edu/mailman/listinfo/ace-bugs

Reply | Forward | Messages in this Topic (5)
#6142 From: Breno Carneiro Pinheiro <brenodee@...>
Date: Sat Oct 10, 2009 8:31 pm
Subject: configure error during cross compiling 		brenodee@...
Send Email Send Email
  
ACE VERSION: 5.7.3

    HOST MACHINE and OPERATING SYSTEM:
       i686-pc-linux

    TARGET MACHINE and OPERATING SYSTEM   
        arm-angstrom-linux-gnueabi
        arm-angstrom-linux-gnueabi-gcc

        gcc-cross-4.1.2-r10
        
    THE $ACE_ROOT/ace/config.h

    THE $ACE_ROOT/include/makeinclude/platform_macros.GNU FILE 

    BUILD METHOD USED:
     mkdir build
     cd build/
     ../configure CXX=path-to-crossbin/arm-angstrom-linux-gnueabi-g++ CC=path-to-crossbin/arm-angstrom-linux-gnueabi-gcc


    CONTENTS OF $ACE_ROOT/bin/MakeProjectCreator/config/default.features
    (used by MPC when you generate your own makefiles):

    AREA/CLASS/EXAMPLE AFFECTED:


    DOES THE PROBLEM AFFECT:
        configuring process error



    SYNOPSIS:
     Message returned:

configure:3630: /home/breno/gumstix/gumstix-oe/tmp/cross/bin/arm-angstrom-linux-gnueabi-g++ -c -g -O2  conftest.cc >&5
conftest.cc: In function 'int main()':

conftest.cc:13: error: 'exit' was not declared in this scope
configure:3636: $? = 1
configure: failed program was:
| /* confdefs.h.  */

configure:3920: /home/breno/gumstix/gumstix-oe/tmp/cross/bin/arm-angstrom-linux-gnueabi-g++ -E  conftest.cc

conftest.cc:12:28: error: ac_nonexistent.h: No such file or directory
configure:3926: $? = 1
configure: failed program was:
| /* confdefs.h.  */
|
| #define PACKAGE_NAME "ACE"

configure:4247: /home/breno/gumstix/gumstix-oe/tmp/cross/bin/arm-angstrom-linux-gnueabi-g++ -o conftest -g -O2   conftest.cc -lfl   >&5

/home/breno/gumstix/gumstix-oe/tmp/cross/lib/gcc/arm-angstrom-linux-gnueabi/4.1.2/../../../../arm-angstrom-linux-gnueabi/bin/ld: cannot find -lfl
collect2: ld returned 1 exit status
configure:4253: $? = 1
configure: failed program was:

| /* confdefs.h.  */


    DESCRIPTION:
    The messages returned shown on synopsis was got during configure process. I couldn't so run make.I decide to attach the log file.

    REPEAT BY:



    SAMPLE FIX/WORKAROUND:


Thanks for any help,
--
Breno Carneiro Pinheiro
_______________________________________________
ace-bugs mailing list
ace-bugs@...
http://list.isis.vanderbilt.edu/mailman/listinfo/ace-bugs

Reply | Forward | Messages in this Topic (5)
Messages 6142 - 6171 of 6171   Newest  |  < Newer  |  Older >  |  Oldest
Message #
Search:
Advanced
Add to My Yahoo!      XML What's This?
Copyright © 2009 Yahoo! Inc. All rights reserved.
Privacy Policy - Terms of Service - Guidelines - Help