The release notes for 0.32 do not list any of the bug fixes that were fixed in 0.31. The related bug description does not have a complete set of files to demonstrate the bug fix. We have chosen the alternative solution (removing virtual destructor declaration).
As an aside: Our implementation was in an attempt to use Google mock for unit testing. We are still working those items out. I may post an inquiry to the community regarding the use of Google mock. Thanks Paul ________________________________________ From: Robbie Gemmell <[email protected]> Sent: Wednesday, September 21, 2016 3:03 AM To: [email protected] Subject: Re: Help! ->qpid::Exception what(): Invalid argument (../include/qpid/sys/posix/Mutex.h:116): QPID - 6416? I can't lend any assistance on the code side, but on the version number...0.31 was the name for the stream of development resulting in the 0.32 release, which confusingly enough contains anything referencing 0.31 or 0.32. We've stopped using that naming style for any of the releases now. Robbie On 20 September 2016 at 21:14, Flores, Paul A. <[email protected]> wrote: > We are grasping at straws. Ran valgrind and it appears issue is occurring in > Connection destructor (~ConnectionIMPL ?). I will post valgrind output > messages when I get them copied over. > > In searching for like issues we came across QPID-6416. But that fixed in > 0.31, right? We did not see any release notes for 0.31 so some uncertainty. > Is there a specific "test" we can run on our side to verify the related fix? > > Working on trying to get a standalone app to illustrate issue but that is a > struggle in itself. > > Suggestions / recommendations are welcomed! > ________________________________________ > From: Gordon Sim <[email protected]> > Sent: Monday, September 19, 2016 3:46 PM > To: [email protected] > Subject: Re: Help! ->qpid::Exception what(): Invalid argument > (../include/qpid/sys/posix/Mutex.h:116) > > On 19/09/16 21:51, Flores, Paul A. wrote: >> Hi, >> >> >> At client site. >> >> >> Performing unit tests and seeing: >> >> >> terminate called after throwing an instance of 'qpid::Exception' >> >> what(): Invalid argument (../include/qpid/sys/posix/Mutex.h:116) >> >> Aborted >> >> >> >> >> Pops up when ~Connection() is called. The destructor is getting called >> automatically. We are not explicitly calling it. >> >> >> Any help would be appreciated to help us to move forward! >> > > Can you isolate a failing test case? The error sounds like a double > deletion of some kind. You could also run your test under valgrind to > see if that shows anything up. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > > ________________________________ > > This communication (including any attachments) may contain information that > is proprietary, confidential or exempt from disclosure. If you are not the > intended recipient, please note that further dissemination, distribution, use > or copying of this communication is strictly prohibited. Anyone who received > this message in error should notify the sender immediately by telephone or by > return email and delete it from his or her computer. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected] ________________________________ This communication (including any attachments) may contain information that is proprietary, confidential or exempt from disclosure. If you are not the intended recipient, please note that further dissemination, distribution, use or copying of this communication is strictly prohibited. Anyone who received this message in error should notify the sender immediately by telephone or by return email and delete it from his or her computer. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
