Le 2017-05-10 11:28, Steven Costiou a écrit : > While configuring my local and remote images to work with the remote > debugger, there was a bug with the menu in the remote browser. So i wanted to > try the debugger and figure out what was the problem using it, but i do not > understand how to proceed. When the debugger opens, all i see is the fact > that there was a remote problem, and that the proxy was unable to return a > proper value. > > I used a local image connected with a headless remote image. To reproduce the > bug, go for example in ByteString >> at:put:, right click after the first dot > and click "debug". See suggs-menu-bug.png. > > When doing that i get debug-win.png and suggs-debug.png and as you can see i > just know there was an error and what it was but i don't have an open > debugger as i would normally expect in Pharo. How can i see the real problem > occuring in the remote image ? How can i remotely fix this considering that > my remote image is headless and it seems to be a problem tied to the remote > thing, because locally it doesn't happen ? (or maybe it is a Calypso problem > but anyway i cannot debug it...) > > Steven.
Hem, i forgot to say that i did that in a remote browser after sending openBrowser to a PRRemotePharo
