[Vm-dev] Fwd: [Pharo-dev] Pharo 7 Repeatable crash: XIO: fatal IO error 14 (Bad address) on X server ":0"

[Eliot Miranda]

Hi Martin,

On Thu, Feb 22, 2018 at 10:45 AM, Martin McClure <martin at hand2mouse.com>
wrote:

>
>
> Anyone here interested in this crash? Is there a newer VM I should test
> with?
>

Certainly try the most up-to-date Vm you can find.  But this looks like
some linux-specific, 32-bit specific bug, because no one else is reporting
crashes like this.  So what I would recommend is that you run from the
command line under gdb and hence that you would be able to get a stack
trace, and maybe even dig a little further.  Such a crash should be due to
something obvious, a null pointer, or a buffer overrun.  And running under
gdb should allow you to narrow in on the bug quite quickly.  If the pharo
vm is compiled with symbols then use the vm itself, otherwise build your
own; you'll need symbols.  If and when the bug is easy to reproduce you can
switch to the debug vm (again you'll have to build it yourself; but builds
these days are easy; checkout, cd, run a build script) and get more
information.

HTH

> Thanks,
>
> -Martin
>
>
> -------- Forwarded Message --------
> Subject: [Pharo-dev] Pharo 7 Repeatable crash: XIO: fatal IO error 14
> (Bad address) on X server ":0"
> Date: Wed, 21 Feb 2018 10:37:18 -0800
> From: Martin McClure <martin at hand2mouse.com> <martin at hand2mouse.com>
> Reply-To: Pharo Development List <pharo-dev at lists.pharo.org>
> <pharo-dev at lists.pharo.org>
> To: Pharo Development List <pharo-dev at lists.pharo.org>
> <pharo-dev at lists.pharo.org>
>
> On the current Linux32 Pharo 7.0, (https://get.pharo.org/70+vm as of 30
> minutes ago) the VM crashes with the message
>
> XIO:  fatal IO error 14 (Bad address) on X server ":0"
>
> whenever I try to enlarge the Pharo window by dragging the corner, and
> get to a size of about 2Mpixels. This is with a virgin image with no
> windows open inside the main window. A workaround seems to be to open a
> System Browser before resizing the main window.
>
> This does not reproduce on Pharo 6.1 (https://get.pharo.org/).
>
> This *does* reproduce when running the Pharo7 image on the Pharo 6.1 VM,
> so it may not be entirely a VM problem.
>
> Most times, no crash dump is created, and nothing is logged to
> PharoDebug.log.
>
> Occasionally, especially when rapidly changing the size of the window,
> it segfaults and logs a dump. This may or may not be the same problem.
>
>
> This is less annoying since I found the workaround, but still seems to
> be something that should be fixed. Does anyone want further information
> from me in order to fix it?
>
> Regards,
>
> -Martin
>
>
>
>
>


-- 
_,,,^..^,,,_
best, Eliot
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.squeakfoundation.org/pipermail/vm-dev/attachments/20180224/7231c5d5/attachment-0001.html>