[ace-users] ACE UDP using ACE_Asynch_Write_Dgram

Steve Huston shuston at riverace.com
Fri Jun 22 11:21:17 CDT 2007


Please use the PROBLEM-REPORT-FORM whenever asking questions on this
list.

The class names would indicate that you're using an added AIO facility
that's not supported as part of ACE. Please contact the provider for
support.

If that organization can't help you, please feel free to contact me to
discuss options for supporting your application.

Best regards,
-Steve

--
Steve Huston, Riverace Corporation
Would you like ACE to run great on your platform?
See http://www.riverace.com/sponsor.htm


> -----Original Message-----
> From: ace-users-bounces at cse.wustl.edu 
> [mailto:ace-users-bounces at cse.wustl.edu] On Behalf Of Jojy Varghese
> Sent: Thursday, June 21, 2007 9:51 PM
> To: ace-users at cse.wustl.edu
> Subject: [ace-users] ACE UDP using ACE_Asynch_Write_Dgram
> 
> 
>  
> Hi All
> 	I am getting an error on the asynchronous callback after a UDP
> send (aio) using ACE_Asynch_Write_Dgram. I was suspecting some
memory
> corruption and hence ran valgrind. Here is what the valgrind output
> shows me. I was wondering why it says "uninitialized byte". Is there
a
> bug in ACE UDP ? As you can see, we are using ACE 5.4 on a linux box
> (IA32).
> 
> 
> 
> 
> ==20530== Syscall param socketcall.sendmsg(msg) points to 
> uninitialised
> byte(s)
> ==20530==    at 0x489F50E: sendmsg (in /lib/libc-2.4.so)
> ==20530==    by 0x41B477B:
> ACE_POSIX_AIO_Select_Provider::do_write_dgram(ACE_POSIX_Asynch
> _Result*)
> (in /usr/lib/libACE.so.5.4.0)
> ==20530==    by 0x41B4C0E:
> ACE_POSIX_AIO_Select_Provider::do_write(ACE_POSIX_Asynch_Result*)
(in
> /usr/lib/libACE.so.5.4.0)
> ==20530==    by 0x41B51A7:
> ACE_POSIX_AIO_Select_Strategy_Base::check(ACE_POSIX_AIO_Select
> _Strategy_
> Base::Handle_Info&) (in /usr/lib/libACE.so.5.4.0)
> ==20530==    by 0x41B6A0F:
> ACE_POSIX_AIO_Select_Strategy::get_next_completed_result(ACE_P
> OSIX_Async
> h_Waiting_List&) (in /usr/lib/libACE.so.5.4.0)
> ==20530==    by 0x41BB1B2:
> ACE_POSIX_AIO_Processor::handle_aio_events_i(ACE_Time_Value*) (in
> /usr/lib/libACE.so.5.4.0)
> ==20530==    by 0x41BB2E6:
> ACE_POSIX_AIO_Processor::handle_aio_events(ACE_Time_Value*) (in
> /usr/lib/libACE.so.5.4.0)
> ==20530==    by 0x41BFCC2:
> ACE_POSIX_AIO_Dispatcher::handle_aio_events(ACE_Time_Value*,
> ACE_POSIX_AIO_Processor*, Thread_Dispatcher&) (in
> /usr/lib/libACE.so.5.4.0)
> ==20530==    by 0x41C15D0:
> ACE_POSIX_AIO_Dispatcher::handle_events(ACE_Time_Value*) (in
> /usr/lib/libACE.so.5.4.0)
> ==20530==    by 0x41A8C61:
> ACE_POSIX_Proactor::handle_events_i(ACE_Time_Value*) (in
> /usr/lib/libACE.so.5.4.0)
> ==20530==    by 0x41A8CC0: ACE_POSIX_Proactor::handle_events() (in
> /usr/lib/libACE.so.5.4.0)
> ==20530==    by 0x4198851: ACE_Proactor::handle_events() (in
> /usr/lib/libACE.so.5.4.0)
> 
> 
> Thanks in advance
> Jojy
> 
> _______________________________________________
> ace-users mailing list
> ace-users at mail.cse.wustl.edu
> http://mail.cse.wustl.edu/mailman/listinfo/ace-users
> 




More information about the Ace-users mailing list