[ace-users] segmentation fault on exit from main()
Johnny Willemsen
jwillemsen at remedy.nl
Tue Sep 25 03:39:53 CDT 2007
Hi,
Thanks for using the PRF form. Probably you have registered an eventhandler
that is already destructed, try to use valgrind to get more information
about the type of event handler.
Regards,
Johnny Willemsen
Remedy IT
Postbus 101
2650 AC Berkel en Rodenrijs
The Netherlands
www.theaceorb.nl / www.remedy.nl
*** Integrated compile and test statistics see
http://scoreboard.theaceorb.nl <http://scoreboard.theaceorb.nl/> ***
*** Commercial service and support for ACE/TAO/CIAO ***
*** See http://www.theaceorb.nl/en/support.html ***
________________________________
From: ace-users-bounces at cse.wustl.edu
[mailto:ace-users-bounces at cse.wustl.edu] On Behalf Of Kim J. Schmock
Sent: Tuesday, September 25, 2007 9:42 AM
To: ace-users at cs.wustl.edu
Subject: [ace-users] segmentation fault on exit from main()
ACE VERSION: 5.5.7 and 5.4.7 (ubuntu package)
HOST MACHINE and OPERATING SYSTEM:
I486-linux-gnu; linux Ubuntu 6.06
COMPILER NAME AND VERSION (AND PATCHLEVEL):
Gcc version 4.0.3 (Ubuntu 4.0.3-lubuntu5)
AREA/CLASS/EXAMPLE AFFECTED:
template <class ACE_SELECT_REACTOR_TOKEN> int
ACE_Select_Reactor_T<ACE_SELECT_REACTOR_TOKEN>::close
(void)
{
ACE_TRACE ("ACE_Select_Reactor_T::close");
ACE_MT (ACE_GUARD_RETURN (ACE_SELECT_REACTOR_TOKEN,
ace_mon, this->token_, -1));
if (this->delete_signal_handler_)
{
delete this->signal_handler_;
this->signal_handler_ = 0;
this->delete_signal_handler_ = 0;
}
this->handler_rep_.close (); <ç========== debug reports
this line
if (this->delete_timer_queue_)
{
delete this->timer_queue_;
DOES THE PROBLEM AFFECT:
EXECUTION:
Exit from main()
SYNOPSIS:
Get a segmentation Fault when exiting main(), when
running on Linux
DESCRIPTION:
After execution of the program, when the Reactor event
handler loop exits, the main exits at the statement return 0;.
Then I receive the message that a segmentation fault
where detected.
It is only on Linux. I dont get any error messages
running on windows (this is of cause another Reactor implementation).
(It is the same code as I posted 19/09 checking
application for memory leaks)
Best regards
/Kim
More information about the Ace-users
mailing list