...and if you aren't confident enough to debug, the way to get help is to provide a minimal test case that reproduces the problem, so that others can try to do that for you. Anyway, it looks like gtkmm is behaving just fine here, so I suspect something is going on between your callback and the rest of the code, e.g. if the captured widget pointer becomes invalidated or etc. (It's not at all clear why it gets the string locally and never uses it, but that shouldn't be a problem.) There's no point trying to guess when we can't see the rest of the code.
On Wed, 29 May 2019 at 11:45, Daniel Boles <[email protected]> wrote: > The sure fire way to figure out what is going on is always to make > complete use of the debugger, i.e. in this case to get and analyse a > backtrace. > >
_______________________________________________ gtkmm-list mailing list [email protected] https://mail.gnome.org/mailman/listinfo/gtkmm-list
