|
|
On 7/7/22 16:10 Jck_01 wrote:
Hello, I have found the code which makes the artefacts on the screen.
There is a callback method which is called when the button is pressed.
In this callback I call the network function of a boost/asio library.
This function writes data to the server. It is just
boost::asio::async_write call. When I commented out this call,
everything was OK - no artefacts at all. So the artefacts are
generated by boost::asio::async_write.
Thanks for the feedback, and it's great that you found the cause.
It's strange since my network library doesn't use FLTK at all!
Yes, such effects shouldn't happen. There's one "standard" error though
that a wild pointer or another pointer going out of scope overwrites
some "random" memory bits and this causes the bugs eventually, sometimes
this happens much later than the original bug. I know, it's a wild
guess, but often this is the reason for such random errors.
I'd recommend to run your program with some memory access checkers
enabled. On Linux (if you can build it there) this would for instance be
'valgrind' but I can't help with Windows if that's the only platform you
can build your program on. Maybe someone else can help you better.
--
You received this message because you are subscribed to the Google Groups "fltk.general" group.
To unsubscribe from this group and stop receiving emails from it, send an email to fltkgeneral+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/fltkgeneral/28953a34-fadb-c161-5af7-19f727d0025b%40online.de.
[ Direct Link to Message ] | |
|
| |