Re: Compiling Protocol-Plugin c++ (MinGW)

Hi there,

I've seen something similar happen with the LINE plugin, which is also
written in C++.  It looked like the C++ engine was freeing the memory when
the plugin_unload() function was called and the main LINE object destructor
was called.

Is your code online somewhere that I can have a play with and attach a few
debuggers to?  Do you also have some backtraces of where it's crashing?
It'd be great to see if its dying in the same place.

Cheers,
Eion

On 21 October 2016 at 07:21, Farc <[email protected]> wrote:

> Hello,
>
> I'm currently developing a protocol-plugin for plugin with c++. But I'm
> struggling with MinGW under Windows 7 (There are no problems on Debian 8
> and g++). Compiling works fine and it runs without crashes, but it crashes
> pidgin when it's exiting.
>
> These are the last lines of output from GDB:
>
> (01:49:33) wpurple: wpurple_cleanup
> (01:49:33) winpidgin: winpidgin_cleanup
> warning: Invalid parameter passed to C runtime function.
>
> warning: Invalid parameter passed to C runtime function.
>
> warning: Invalid parameter passed to C runtime function.
>
> warning: Invalid parameter passed to C runtime function.
>
> Without GDB Windows 7(64bit) presents an error message.
>
> I thought it might have something to do with my code. So I reduced my
> plugin to really simple block of code which is just needed by pidgin to be
> recognized as a protocol plugin. And the same happens when exiting. But if
> I compile it in c-mode (I've tried alot of stuff...) pidgin exits normal
> without crashing.
>
> Hopefully someone can help me. Thx
>
> _______________________________________________
> Devel mailing list
> [email protected]
> https://pidgin.im/cgi-bin/mailman/listinfo/devel

_______________________________________________
Devel mailing list
[email protected]
https://pidgin.im/cgi-bin/mailman/listinfo/devel