[erlang-bugs] R14B02+ crashes on older hardware, Windows XP

Patrick Baggett <>
Sat Jul 2 09:00:56 CEST 2011


The attached logged are pretty much useless. They are more or less hardware
specs, but they don't even say the reason the program crashed (e.g.
segfault, bus error, invalid insn, etc.) That error dialog that you have a
screenshot of: try clicking the blue underlined link "click here" and
reading the crash code. It will be 8 hex digits, usually beginning with
C000, for example, C000001D is "illegal instruction" which can occur in an
older CPU tries to execute newer instructions.

Patrick

On Fri, Jul 1, 2011 at 11:29 PM, sgm <> wrote:

> We have a field data collection application recently re-written to use
> CouchDB. It requires minimal computer resources, so a number of the
> notebooks we use are circa 2001/2002. All run Windows XP with SP2 or
> SP3, and we are using CouchDB 1.1.
>
> On the older machines, Erlang R14B02 and R14B03 crash almost
> immediately upon running werl or erl. R14B01 does not.
>
> I'm attaching a screenshot of the crash on one of the machines. In all
> cases it happens at the same point, almost immediately, is 100%
> reproducible, and no crash dump is generated.
>
> Here are the machines where it crashes:
>
> Dell Inspiron 2500, 1.0GHz Pentium III, 160MB RAM, system summary
> rctc11.txt attached
> Dell Inspiron 2600, 1.06GHz Celeron, 128MB RAM, system summary
> rctc12.txt attached
> Gateway Solo 9300, 750MHz Pentium III, 160MB RAM, system summary
> rctc16.txt attached
>
> For comparison, I'm also including this machine of similar vintage
> which does NOT crash:
>
> Dell Inspiron 2650, 1.7GHz Pentium 4, 256MB RAM, system summary
> rctc13.txt attached
>
> Please let me know if you need more information or if there is
> anything you'd like me to try. Thanks,
>
> Steve
>
> _______________________________________________
> erlang-bugs mailing list
> 
> http://erlang.org/mailman/listinfo/erlang-bugs
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://erlang.org/pipermail/erlang-bugs/attachments/20110702/85f690d1/attachment.html>


More information about the erlang-bugs mailing list