Open browser only after gdbgui server is fully started #504
Description
Hi,
I’ve noticed that when launching gdbgui, the browser opens immediately before the server has fully started and begun listening on the specified port. This causes a “Unable to connect” error in the browser on first load, which can confuse users.
A more robust approach would be to open the browser only after the server has successfully bound to the port and is ready to accept connections. This event-driven logic ensures the browser attempts to connect when the server is truly available, improving user experience and eliminating race conditions.
Currently, introducing a fixed wait/sleep before opening the browser is a workaround but not ideal, as startup times vary across systems.
Thanks for the great tool!