That is much more serious than a warning. I'd expect it to be
immediately followed by a crash with signal 3 (abort), rather than
signal 11 (segmentation fault). However, if this isn't the standard
assert routine, I would expect any attempt to actually use hash_table to
produce a segmentation fault.
The standard assert routine is a macro which tests the condition and, if
it fails, logs the fact then call abort, which never returns.
On 11/03/18 21:49, Thomas Kluge wrote:
(k3util:2054): GLib-CRITICAL **: g_hash_table_insert_internal:
assertion 'hash_table != NULL' failed
I think this is just a warning but it was followed by a segfault...
______________________________________________________________
Elecraft mailing list
Home: http://mailman.qth.net/mailman/listinfo/elecraft
Help: http://mailman.qth.net/mmfaq.htm
Post: mailto:Elecraft@mailman.qth.net
This list hosted by: http://www.qsl.net
Please help support this email list: http://www.qsl.net/donate.html
Message delivered to arch...@mail-archive.com
