[erlang-bugs] Crash in wxErlang (17 rc1)

[Dan Gudmundsson]

Well the documentation is minimal, so I suggest you take a look at the
samples
in the wx/examples directory.

After the minimal and hello world examples:
Run wx:demo(). which have exemplifies some more widgets with code displayed.
The demo needs more examples, so if you want to start with something simple
patches are accepted :-)

Larger and probably better code is in observer, as we/I learn wxWidgets the
more
we use it.

But yes wx is a just a thin wrapper on top of wxWidgets so if you do stuff
that is not
expected or wrong it will crash. I have tried to hinder crashes as much as
I could.

To be safe from crashes somebody will have to write a layer on top wx which
keeps
a state of what is happening and what is allowed, a gs on top wx..

/Dan
PS: Steve I have set you up here :-)






On Fri, Feb 7, 2014 at 7:29 AM, Jeff Davis <pgsql@REDACTED> wrote:

> On Thu, 2014-02-06 at 08:35 +0100, Dan Gudmundsson wrote:
> > What are you trying to do?
> >
> >
> > That code seg faults on all releases,
> > you will always be able to crash wx if you try.
> >
> >
> > If you write that code in C++ it will crash as well.
> >
> I'm trying to learn both erlang and wx.
>
> As a user, my understanding of erlang is that it is not supposed to
> segfault unless I have some misbehaving NIF or something. Are there
> other built-in libraries that can cause crashes?
>
> I was actually pretty happy with gs because it's so simple, but I see
> that it's deprecated now.
>
> Regards,
>         Jeff Davis
>
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://erlang.org/pipermail/erlang-bugs/attachments/20140207/796c7d0e/attachment.htm>