Catching a hot potato

[Steven Schveighoffer]

On Mon, 17 Oct 2011 09:04:06 -0400, Gor Gyolchanyan  
<gor.f.gyolchanyan at gmail.com> wrote:

> I see. That's what i said: overwritten allocated memory is the
> hardest-to-find bug.
> But you've shown me, that i can't possibly track down the misbehaving
> module by catching a sigsegv.
> There has to be a way to make thrid-party DLL usage safe and rid the
> user from dunno-why crashes.
> The user at least needs to know which DLL to throw away.
> Any ideas how it could be achieved?

No.  How do you know which DLL is the culprit?

As others have said, some modern browsers have eschewed the DLL model for  
a process-based one in order to prevent crashes of the whole application.

My suggestion would be to create some sort of IPC via shared  
memory/semaphores.  That should be quite fast, and then the damage is only  
limited to shared memory.

-Steve