|
From: John A <jo...@ar...> - 2021-03-26 17:41:21
|
Hey y'all, I am attempting to solve a unique problem with our inhouse software. The main client and server are C/C++. There is also a GUI server using wxWidgets 3.1. Any guidance to this would be helpful: many or 1 client(s) are begun and connect locally or via TCP to the server GUI instance. When a client disconnects, the server GUI segfaults. We're using Boost 1.74/1.76 (rc2) Best regards, John aronetics.com We Speak ITR +1-216/307-5760 |
|
From: Philippe W. <phi...@sk...> - 2021-03-26 18:37:32
|
Looks a little bit difficult to tell anything precise based on the info you provide.
As general guidelines:
* If the server segfaults, you should have a core dump to debug and see what went wrong.
If core dump is disabled (e.g. check ulimit -a), you might also just
attach with gdb and have gdb stop when the segfault is encountered.
* And of course, you can try to run your program under valgrind.
Philippe
On Fri, 2021-03-26 at 13:22 -0400, John A wrote:
> Hey y'all,
>
> I am attempting to solve a unique problem with our inhouse software. The
> main client and server are C/C++. There is also a GUI server using wxWidgets
> 3.1.
>
> Any guidance to this would be helpful: many or 1 client(s) are begun and
> connect locally or via TCP to the server GUI instance. When a client
> disconnects, the server GUI segfaults.
>
> We're using Boost 1.74/1.76 (rc2)
>
> Best regards,
> John
>
> aronetics.com
> We Speak ITR
> +1-216/307-5760
>
>
>
>
> _______________________________________________
> Valgrind-users mailing list
> Val...@li...
> https://lists.sourceforge.net/lists/listinfo/valgrind-users
|