g_signal_handlers_disconnect_matched: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed (Issue #22619)

596 views
Skip to first unread message

Krzysztof J. Ksor

unread,
Jul 9, 2022, 3:54:35 AM7/9/22
to wx-...@googlegroups.com, Subscribed

sample/concole.cpp

when compile it with
$g++ -Wall -pedantic -pedantic-errors wx-config-3.0 --cxxflags --unicode -DwxUSE_GUI=0 wx-config-3.0 --cxxflags --unicode wx-config-3.0 --libs --unicode console.cpp -o co
and run I get

./co

Welcome to the wxWidgets 'console' sample!
For more information, run it again with the --help option

(process:6900): GLib-GObject-WARNING **: 09:49:18.971: invalid (NULL) pointer instance

(process:6900): GLib-GObject-CRITICAL **: 09:49:18.971: g_signal_handlers_disconnect_matched: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed

(process:6900): GLib-GObject-WARNING **: 09:49:18.971: invalid (NULL) pointer instance

(process:6900): GLib-GObject-CRITICAL **: 09:49:18.971: g_signal_handlers_disconnect_matched: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed

where is different notma compiling and my compiling?


Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.Message ID: <wxWidgets/wxWidgets/issues/22619@github.com>

VZ

unread,
Jul 15, 2022, 6:56:14 PM7/15/22
to wx-...@googlegroups.com, Subscribed

Are you compiling the sample from 3.1.7 using wx-config from 3.0 intentionally? This also explains your error due to the use of wxCMD_LINE_HIDDEN which doesn't exist in 3.0.

Anyhow, I can't reproduce the problem when building the sample in 3.2.0 normally, so I strongly suspect some local problem. But if not, please try debugging the messages above by running the sample under gdb and breaking on g_log_writer_standard_streams and then use bt to see where these messages come from.


Reply to this email directly, view it on GitHub, or unsubscribe.

You are receiving this because you are subscribed to this thread.Message ID: <wxWidgets/wxWidgets/issues/22619/1186008328@github.com>

Krzysztof J. Ksor

unread,
Jul 21, 2022, 1:20:15 PM7/21/22
to wx-...@googlegroups.com, Subscribed

no problem ;-) reproduce

$uname -a
Linux localhost.localdomain 5.11.22-100.fc32.x86_64 #1 SMP Wed May 19 18:58:25 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux
$wx-config-3.0 --version
3.0.4

just type make
https://github.com/xor256/error-cl


Reply to this email directly, view it on GitHub, or unsubscribe.

You are receiving this because you are subscribed to this thread.Message ID: <wxWidgets/wxWidgets/issues/22619/1191745151@github.com>

VZ

unread,
Jul 21, 2022, 1:57:02 PM7/21/22
to wx-...@googlegroups.com, Subscribed

Is it related to setting Polish locale? I don't have it on my system, so the output is:

19:53:14: Warning: Cannot set locale to language "Polish".
start [0]
OK
stop [0]
ilo?? argument?w programu './a.out': 1

but changing it to wxLANGUAGE_FRENCH makes the program run successfully.

Please try debugging this (compile and link with -g) and try putting a breakpoint on g_log_writer_standard_streams to at least see where are these messages coming from.


Reply to this email directly, view it on GitHub, or unsubscribe.

You are receiving this because you are subscribed to this thread.Message ID: <wxWidgets/wxWidgets/issues/22619/1191777067@github.com>

Krzysztof J. Ksor

unread,
Jul 21, 2022, 3:30:37 PM7/21/22
to wx-...@googlegroups.com, Subscribed

How?


Reply to this email directly, view it on GitHub, or unsubscribe.

You are receiving this because you are subscribed to this thread.Message ID: <wxWidgets/wxWidgets/issues/22619/1191855946@github.com>

VZ

unread,
Jul 21, 2022, 4:21:00 PM7/21/22
to wx-...@googlegroups.com, Subscribed

  1. You not type 'make' why? this is important because i show how compile it

I've executed exactly the same g++ command you've shown. In any case, this shouldn't have any effect.

2. How? using debug?

Yes:

  1. Compile and link with -g.
  2. Run gdb ./cl
  3. Do start, then b g_log_writer_standard_streams, then continue.
  4. When gdb stops on the breakpoint, type bt to see where the function is called from.


Reply to this email directly, view it on GitHub, or unsubscribe.

You are receiving this because you are subscribed to this thread.Message ID: <wxWidgets/wxWidgets/issues/22619/1191896204@github.com>

Krzysztof J. Ksor

unread,
Jul 21, 2022, 5:16:24 PM7/21/22
to wx-...@googlegroups.com, Subscribed

  1. You run ./a.out not ./cl ;-) therefore i think You not use my make ;-)
  2. i must download 5GiB packages to run this ......


Reply to this email directly, view it on GitHub, or unsubscribe.

You are receiving this because you are subscribed to this thread.Message ID: <wxWidgets/wxWidgets/issues/22619/1191943203@github.com>

0xtrzy

unread,
Jul 22, 2022, 1:06:50 PM7/22/22
to wx-...@googlegroups.com, Subscribed

yes, I have this same eror from repo example

start [0]

OK

stop [0]

ilość argumentów programu './cl': 1



(process:5228): GLib-GObject-WARNING **: 19:09:35.627: invalid (NULL) pointer instance



(process:5228): GLib-GObject-CRITICAL **: 19:09:35.628: g_signal_handlers_disconnect_matched: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed



(process:5228): GLib-GObject-WARNING **: 19:09:35.628: invalid (NULL) pointer instance



(process:5228): GLib-GObject-CRITICAL **: 19:09:35.628: g_signal_handlers_disconnect_matched: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed

fedora 32 x86
wx 3.0.4


Reply to this email directly, view it on GitHub, or unsubscribe.

You are receiving this because you are subscribed to this thread.Message ID: <wxWidgets/wxWidgets/issues/22619/1192774107@github.com>

VZ

unread,
Jul 22, 2022, 1:31:40 PM7/22/22
to wx-...@googlegroups.com, Subscribed

Thanks, as @xor256 edited their comment I didn't notice the stack.

Looking at it, it's immediately clear that this was fixed back in 17de4e3 (Avoid using NULL GtkSettings pointer, 2017-11-25) which was backported into 3.0 branch as 904c32c and is part of 3.0.5.

So this bug was fixed a long time ago, I don't know why does Fedora still have 3.0.4. And, of course, 3.1.7 in the original bug report was wrong, as this bug was fixed in 3.1 back in 3.1.1.


Reply to this email directly, view it on GitHub, or unsubscribe.

You are receiving this because you are subscribed to this thread.Message ID: <wxWidgets/wxWidgets/issues/22619/1192792714@github.com>

VZ

unread,
Jul 22, 2022, 1:37:31 PM7/22/22
to wx-...@googlegroups.com, Subscribed

Closed #22619 as completed.


Reply to this email directly, view it on GitHub, or unsubscribe.

You are receiving this because you are subscribed to this thread.Message ID: <wxWidgets/wxWidgets/issue/22619/issue_event/7048081761@github.com>

Scott Talbert

unread,
Jul 22, 2022, 1:45:54 PM7/22/22
to wx-...@googlegroups.com, Subscribed

So this bug was fixed a long time ago, I don't know why does Fedora still have 3.0.4. And, of course, 3.1.7 in the original bug report was wrong, as this bug was fixed in 3.1 back in 3.1.1.

Fedora 32 was EOL on 2021-05-25. @xor256, I would strongly recommend that you upgrade to a supported Fedora release, 35 or newer.

Supported Fedoras have 3.0.5.1 and some variant of 3.1.5+.


Reply to this email directly, view it on GitHub, or unsubscribe.

You are receiving this because you are subscribed to this thread.Message ID: <wxWidgets/wxWidgets/issues/22619/1192803120@github.com>

Reply all
Reply to author
Forward
0 new messages