Hi all: I've been working with OpenMAMA for a little while now as part of my "day job", and I've also been working with static analysis tools for some time, so I thought it would be fun to put the two

Hi Damian: Thanks for the feedback. I’ve made some comments below. Regards, Bill Right now, getting static analysis working with other tools is somewhat dependent on the build tooling. I use a custom

Hi All: I’ve completed a draft version of my latest article on static analysis, using clang and cppcheck on the OpenMAMA code. It can be found at: http://btorpey.github.io/lots-o-static/ I’m very inte

Unfortunately, that is not a bug, but a “feature”. The problem is that mama_close unloads both the transport and payload libraries (via dlclose on Linux). So, any access to any objects related to eith

Sanjeev: Thanks for the suggestion, but that is basically doing C-style manual memory management. That’s not a direction I’m interested in going — it’s the 21st century, and OpenMAMA needs to get with

HI Frank: And Happy Holidays to you too! A couple of points: I’m not aware of any changes to OpenMAMA that affect the issue, so if there are some please point me in the proper direction. The last repl

See comments inline … No, we shut down the bridges to prevent events from firing. In some cases (and certainly *not* all) that also releases resources acquired when the bridges were opened, which is a

Hi Frank: Obviously I would prefer to remain as close as possible to upstream code, so forking is a last resort. That being said, you’ve been so far quite unreceptive to my concerns about crashing as

P.S. The bit about maintaining fixes etc. works both ways — once someone does a hard fork, there is less incentive for them to contribute fixes and improvements upstream. As the project maintainer I w

Hi Frank: Why don’t we start over here and see if we can make some progress? If you’re OK with a solution based on a mama.properties setting, I can live with that. For the transport it seems to me tha

As far as I can tell, there’s no perfect solution here. From https://linux.die.net/man/3/pthread_mutex_destroy So you either destroy the locked mutex, which is UB, or you unlock it first. In the secon

At first glance, that sounds like just “kicking the can down the road” — i.e., you’re still left with the problem of what to do with these wrappers such that you can tear them down in a thread-safe ma

Hi Frank: At NYFIX we not too long ago moved from RH to CentOS 7 for our dev and prod installs, and assumed that CentOS 8 would be our eventual upgrade path. It’s way too early to say how things shake