![]() |
Common issues. - Printable Version +- ScratchPad Forums (https://www.scratchpadgames.net/forums2) +-- Forum: Scratchpad Forums (https://www.scratchpadgames.net/forums2/forumdisplay.php?fid=1) +--- Forum: General (https://www.scratchpadgames.net/forums2/forumdisplay.php?fid=2) +--- Thread: Common issues. (/showthread.php?tid=10) |
Common issues. - bbeuken - 06-05-2025 Lets put a lilst of common issues here so they are in one place. And we'll start with the most common of all Could not connect to the remote system or the connection was lost. If this is happening on your 1st attempt to connect, make sure your cables are plugged in, Bookworm can be annoyingly fussy about making connections and sometimes you might have to set up a fixed IP on your Pi and address it directly. I havn't found a fool proof way to get round this. 90% of systems just connect, 10% spend forever attempting to connect then report failure... If using the .local naming method, always make sure you have referenced the targets name correctly in your cross platform settings. if you have, try to use its IP address instead, because sometimes when you switch things off, you might lose the link between the .local name and the ip address it saved when you set it up. If you connected correctly beforehand, go to Debug->Options>Crossplatform, and try verifying your connection and make sure you are defaulting to your correct target. If it fails to verify, remove it, and reinstall it as a target. It may then connect but you will have to do a rebuild 1 time to re-establish the connection between your PC and Pi. Exception Unhandled, segmentation fault Now usually these are very specific to bad pointers which will be mostly down to your code, but there's one very common one, if it occurs in the Xwindow.cpp file when you try to get Rootwindow, it means you system was unable to open your default window. Two main causes for that, 1, if you initially fired your target up while not connected to a monitor, it will have no display and therefore will have no pointer.. 2, more common, you somehow don't have export DISPLAY=:0.0 as your pre-launch command in the debugging ->Pre-launch command setting of your (raspberry) properties. . |