It seems that is trying to destroy an IupImage that is already destroyed.
I can't go further without more context.

  Can you reproduce the problem in a small sample?

Best,
Scuri


Em sex, 24 de mai de 2019 às 16:33, Ranier VF <ranier_...@hotmail.com>
escreveu:

> Hi,
> I'm around with a IUP bug. Below show the callstack:
>  may be wrong.
> 1288cfb0 00000111 0000006a iup!iupObjectCheck+0x8
> 1288cfb0 00000111 0000006a iup!iupdrvImageDestroy+0x2dbf
> 000303de 00000111 0000006a iup!iupwinBaseMsgProc+0x61f
> 03df3160 000303de 00000111 USER32!GetDC+0x6d
> 00000000 03df3160 000303de USER32!GetDC+0x14f
> 005fc5a8 025f8a60 0000006a USER32!GetParent+0x16c
> 000303de 00000111 0000006a USER32!SendMessageW+0x49
> 025fc658 00000000 025fc658 USER32!CreateMDIWindowA+0x1bd
> 074f4fc4 00000001 00000000 USER32!DeregisterShellHookWindow+0x6312
> 025fc658 00000202 00000000 USER32!IsDlgButtonChecked+0x109a
> 00a1036e 00000202 00000000 USER32!IsDlgButtonChecked+0x437
> 7e3751d1 00a1036e 00000202 USER32!GetDC+0x6d
> 00000000 7e3751d1 00a1036e USER32!GetDC+0x14f
> 7e3751d1 00a1036e 00000202 USER32!IsWindowUnicode+0xa1
> 7e3751d1 00a1036e 00000202 USER32!CallWindowProcW+0x1b
> 00a1036e 00000202 00000000 iup!iupwinBaseMsgProc+0x657
> 03df3160 00a1036e 00000202 USER32!GetDC+0x6d
> 00000000 03df3160 00a1036e USER32!GetDC+0x14f
> 0012fe1c 00000000 7e36929b USER32!GetWindowLongW+0x127
> 0012fe1c 0127f6ee 0127f742 USER32!DispatchMessageW+0xf
> 7c929f95 050f6f68 003943a0 iup!IupMainLoop+0xa6
> 00000001 050f0fd0 05098f68 accman!main(int argc = <Memory access error>,
> char ** argv = <Memory access error>)+0x200 (FPO: [Non-Fpo]) (CONV: cdecl)
> [c:\usr\src\accman\app.c @ 182]
> 0012fff0 7c817067 0127f6ee accman!__tmainCRTStartup(void)+0x1bf (FPO:
> [Non-Fpo]) (CONV: cdecl) [f:\dd\vctools\crt_bld\self_x86\crt\src\crtexe.c @
> 555]
> 0127f6ee 0127f742 7ffd5000 accman!mainCRTStartup(void)+0xf (FPO:
> [Non-Fpo]) (CONV: cdecl) [f:\dd\vctools\crt_bld\self_x86\crt\src\crtexe.c @
> 371]
> 00480b70 00000000 78746341 KERNEL32!RegisterWaitForInputIdle+0x49
>
> iupObjectCheck raise segmentation fault with access violation.
> Unfortunately, dont have iup lib with full debug symbols.
>
> Best regards,
> Ranier Vilela
>
> _______________________________________________
> Iup-users mailing list
> Iup-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/iup-users
>
_______________________________________________
Iup-users mailing list
Iup-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/iup-users

Reply via email to