[interprocess] Crash of singleton_module in Windows
Steps to reproduce the problem: * Create singleton_dll.dll. * Create singleton_exe.exe, which uses singleton_dll.dll. * Run. On exit, an access violation happens. Seemingly, the problem happens when two different singletons are created, one in the main executable and the other in a DLL. If both singletons are created in the same module everything's OK, though. Best regards, Joaquín M López Muñoz Telefónica Digital ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra política de envío y recepción de correo electrónico en el enlace situado más abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at. http://www.tid.es/ES/PAGINAS/disclaimer.aspx
El 12/01/2012 21:41, JOAQUIN M. LOPEZ MUÑOZ escribió:
Steps to reproduce the problem:
* Create singleton_dll.dll. * Create singleton_exe.exe, which uses singleton_dll.dll. * Run. On exit, an access violation happens.
Seemingly, the problem happens when two different singletons are created, one in the main executable and the other in a DLL. If both singletons are created in the same module everything's OK, though.
Do you know if this appeared in Boost 1.48? Best, Ion
El 12/01/2012, a las 22:46, "Ion Gaztañaga" <igaztanaga@gmail.com> escribió:
El 12/01/2012 21:41, JOAQUIN M. LOPEZ MUÑOZ escribió:
Seemingly, the problem happens when two different singletons are created, one in the main executable and the other in a DLL. If both singletons are created in the same module everything's OK, though.
Do you know if this appeared in Boost 1.48?
I *think* it's an after-48 problem. Joaquín M López Muñoz Telefónica Digital Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra política de envío y recepción de correo electrónico en el enlace situado más abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at. http://www.tid.es/ES/PAGINAS/disclaimer.aspx
El 12/01/2012 23:18, JOAQUIN M. LOPEZ MUÑOZ escribió:
El 12/01/2012, a las 22:46, "Ion Gaztañaga"<igaztanaga@gmail.com> escribió:
El 12/01/2012 21:41, JOAQUIN M. LOPEZ MUÑOZ escribió:
Seemingly, the problem happens when two different singletons are created, one in the main executable and the other in a DLL. If both singletons are created in the same module everything's OK, though.
Do you know if this appeared in Boost 1.48?
I *think* it's an after-48 problem.
Ok, thanks Ion
Ion Gaztañaga <igaztanaga <at> gmail.com> writes:
El 12/01/2012 23:18, JOAQUIN M. LOPEZ MUÑOZ escribió:
El 12/01/2012, a las 22:46, "Ion Gaztañaga"<igaztanaga <at> gmail.com>
escribió:
El 12/01/2012 21:41, JOAQUIN M. LOPEZ MUÑOZ escribió:
Seemingly, the problem happens when two different singletons are created, one in the main executable and the other in a DLL. If both singletons are created in the same module everything's OK, though.
Do you know if this appeared in Boost 1.48?
I *think* it's an after-48 problem.
Ok, thanks
Do you want me to file a ticket? Joaquín M López Muñoz Telefónica Digital
Joaquin M Lopez Munoz wrote
Steps to reproduce the problem:
* Create singleton_dll.dll. * Create singleton_exe.exe, which uses singleton_dll.dll. * Run. On exit, an access violation happens.
Seemingly, the problem happens when two different singletons are created, one in the main executable and the other in a DLL. If both singletons are created in the same module everything's OK, though.
Best regards,
Hi Joaquín, is there a way to make evident the issue without using directly the ipcdetail namespace? Best, Vicente -- View this message in context: http://boost.2283326.n4.nabble.com/interprocess-Crash-of-singleton-module-in... Sent from the Boost - Dev mailing list archive at Nabble.com.
Vicente Botet <vicente.botet <at> wanadoo.fr> writes:
Joaquin M Lopez Munoz wrote
Steps to reproduce the problem:
* Create singleton_dll.dll. * Create singleton_exe.exe, which uses singleton_dll.dll. * Run. On exit, an access violation happens.
Seemingly, the problem happens when two different singletons are created, one in the main executable and the other in a DLL. If both singletons are created in the same module everything's OK, though.
Best regards,
Hi Joaquín,
is there a way to make evident the issue without using directly the ipcdetail namespace?
This has arisen in connection with an issue in Boost.Flyweight: https://svn.boost.org/trac/boost/ticket/6382 intermodule_singleton is an internal component of Boost.Interprocess (besides being used by Boost.Flyweight with kind permission from Ion) so I guess there's a way to expose this problem also from the public interface of Boost.Interprocess. Joaquín M López Muñoz Telefónica Digital
participants (4)
-
Ion Gaztañaga -
JOAQUIN M. LOPEZ MUÑOZ -
Joaquín M López Muñoz
-
Vicente Botet