Smalltalk › Pharo › Pharo Smalltalk Users

VM crash on Ubuntu 14.04

_‹ Previous Topic Next Topic _›

Classic

List

Threaded

24 messages Options

Ben Coman

Re: VM crash on Ubuntu 14.04

On Fri, Oct 30, 2015 at 2:03 AM, Johan Fabry <[hidden email]> wrote:
>
> OK, back with access to the Ubuntu machine, I reproduced the crash when
> running under gdb (reproducing it is never an issue, finding the minimal
> case is the issue). See below for gdb output. But my vm has no debug
> information compiled, so it is not really useful. Can I download a vm with
> debug info compiled from somewhere? I would prefer to avoid having to
> download the sources and compile et cetera …

Why not give it a go? :) I found it dead simple to compile the VM for
the first time following instructions at...
[1] https://github.com/pharo-project/pharo-vm

This was on OSX and the only problem I had was _not_ following the
instructions and using XCode 10.9 instead of 10.6.
I can't speak for Ubuntu but its the reference Unix platform. I guess
you'll get better support getting started with the standard
instructions (since we'd like them "perfect" and more people will be
able to replicate a problem with these than replicate your unique
problem)

One thing though, could someone update [1] to describe how to get a
debug VM, since that must be a common reason someone wants to compile
their own VM for the first time. I hunted around for some info but
could only find tips from a few years ago and I'm not sure if they
still apply

Debug a VM (by Mariano)
https://marianopeck.wordpress.com/2011/04/10/building-the-vm-from-scratch-using-git-and-cmakevmmaker/
https://marianopeck.wordpress.com/2011/04/16/building-the-vm-second-part/
https://vimeo.com/22485382 (PharoCast)

Debugging assembly in Pharo VM with GDB (by Melkyades)
http://melkyades.blogspot.com.au/2013/07/debugging-assembly-in-pharo-vm-with-gdb.html

cheers -ben

>
> Once I have such a VM I will make some time to further investigate, and
> report results.
>
> Program received signal SIGSEGV, Segmentation fault.
> 0xb8c2bc31 in ?? ()
> (gdb) bt
> #0 0xb8c2bc31 in ?? ()
> #1 0x080fc9f2 in primitiveNativeCall ()
> #2 0xb4fba770 in ?? ()
> #3 0xb503b05e in ?? ()
> #4 0xb503afcb in ?? ()
> #5 0xb5011abd in ?? ()
> #6 0xb4fba5c0 in ?? ()
> (gdb)
>
> On Oct 27, 2015, at 19:09, Nicolai Hess <[hidden email]> wrote:
>
>
>
> 2015-10-26 15:03 GMT+01:00 Johan Fabry <[hidden email]>:
>>
>> Hi Nicolai,
>>
>> thanks for following up on this.
>>
>> I am in the process of determining what causes the crash. I fear that to
>> reproduce the problem you will need to have ROS installed, I have not yet
>> been able to reproduce it without ROS running. I do not want to inflict the
>> installation of ROS on you without being 100% sure.
>>
>> I am using Roassal because this is for Live Robot Programming
>> (http://pleiad.cl/LRP) which uses a dynamic visualization of the running
>> code. To reproduce the bug (until now) I need to develop code in LRP when
>> using ROS, and then it happens randomly. I realize that this is too much to
>> ask for an outsider to reproduce the bug (I did not expect anybody to
>> download and install PhaROS to try to reproduce, thanks for that!!).
>>
>> Can you inform me how I can get you more useful debug info to you? I will
>> keep trying to find minimal steps to reproduce in the mean time.
>
>
> No, the best we can hope for is a crash when it is running from debugger,
> you can start the vm with a debugger or attach the debugger to a running
> process. If we are lucky, the debugger will show a stacktrace.
>
>>
>>
>> On Oct 24, 2015, at 19:45, Nicolai Hess <[hidden email]> wrote:
>>
>> Can you provide the image file.
>> What exactly runs in the image (does it depend on ROS or
>> does it crash even without it). For what do you
>> use Roassal in this environment.
>> Can you reproduce the crash with a clean image (and maybe loading
>> some package - without all of the ROS-stuff?
>> (I just followed the installation guide for PhaROS, but I have no idea
>> how to go from here to do anything to reproduce the crash).
>>
>>
>>
>> 2015-10-24 21:32 GMT+02:00 Johan Fabry <[hidden email]>:
>>>
>>>
>>> Ben, thanks for replying but since no VM guys are following up on this,
>>> apparently, it does not make much sense for me to go this way.
>>>
>>> Guys, am I to assume there is not help for me on this topic?
>>>
>>> > On Oct 23, 2015, at 11:03, Ben Coman <[hidden email]> wrote:
>>> >
>>> > On Thu, Oct 22, 2015 at 2:25 AM, Johan Fabry <[hidden email]>
>>> > wrote:
>>> >> Hi all,
>>> >>
>>> >> I am having some unpleasant experiences on Ubuntu 14.04 (experimenting
>>> >> with Live Robot Programming on PhaROS). The VM crashes after a random amount
>>> >> of time (< 25 minutes), with no clear sequence of steps on how to reproduce
>>> >> the crash. I am using Pharo 4 (Pharo 40622 as installed by PhaROS) + Roassal
>>> >> which required an install of libcairo2:i386 . VM version details below.
>>> >>
>>> >> There is no printout on stdout, and the debug.log does not contain
>>> >> recent entries (timestamp is always some minutes before the actual crash
>>> >> happens).
>>> >>
>>> >> Is this a known problem? If so, how can I fix it, and if not how can I
>>> >> provide more debugging info?
>>> >>
>>> >> Thanks in advance!
>>> >
>>> > I'm not much help since I haven't done these myself, but just some
>>> > ideas (maybe someone can add more details)
>>> > * compile and run a debug vm
>>> > * trace all function calls, http://tinyurl.com/gdb-trace-all
>>> >
>>>
>>>
>>>
>>> ---> Save our in-boxes! http://emailcharter.org <---
>>>
>>> Johan Fabry - http://pleiad.cl/~jfabry
>>> PLEIAD and RyCh labs - Computer Science Department (DCC) - University
>>> of Chile
>>>
>>>
>>
>>
>>
>>
>> ---> Save our in-boxes! http://emailcharter.org <---
>>
>> Johan Fabry - http://pleiad.cl/~jfabry
>> PLEIAD and RyCh labs - Computer Science Department (DCC) - University
>> of Chile
>
>
>
>
> ---> Save our in-boxes! http://emailcharter.org <---
>
> Johan Fabry - http://pleiad.cl/~jfabry
> PLEIAD and RyCh labs - Computer Science Department (DCC) - University of
> Chile
>

EstebanLM

Re: VM crash on Ubuntu 14.04

In reply to this post by stepharo

Ben, thanks for replying but since no VM guys are following up on this, apparently, it does not make much sense for me to go this way.

Yep, that hurts.

Guys, am I to assume there is not help for me on this topic?

And that hurts even more.

I’m *trying* to help you, but so far you provided almost none information (is like going to the doctor and say “I feel bad”).

Even without information I told you “is the heap”. Now I will told you something more: a debug vm will not help you much because you are running out of resources *in the HEAP*.

try expanding memory and monitoring memory consumption to see how it goes.

try forcing free of resources in your visualisations or anything “FFI Related”.

cheers,

Esteban

ps: And yes, we need to update the “debug vm build” info in the instructions, but is just affecting on line or so :)

pps: And we also could provide some debug vms for this cases. I cannot schedule the time now for doing the jobs, but I will put it in my TODO list.

jfabry

Re: VM crash on Ubuntu 14.04

Whoa guys, sorry for all this but there is some miscommunication going on here. Steph was replying now to an old mail of mine. I said that because for a number of days I had no replies to my initial report. So *at that time* no VM guys were following up on this and I was lost and helpless. I don’t know anything about building VM’s and nothing about how to debug them.

This is clearly no longer the case. I have had a lot of help this week and I *do* appreciate the feedback you guys have been giving me! I know I am not giving a lot of useful information but the setup is complicated, and I have extremely limited knowledge about how to debug native apps in Linux. So I am doing all that I can and I am happy to receive whatever pointers may be useful.

We will investigate more with Ronie this week I am sure that with his help we will move forward much more smoothly.

On Nov 1, 2015, at 08:26, Esteban Lorenzano <[hidden email]> wrote:

Ben, thanks for replying but since no VM guys are following up on this, apparently, it does not make much sense for me to go this way.

Yep, that hurts.

Guys, am I to assume there is not help for me on this topic?

And that hurts even more.

I’m *trying* to help you, but so far you provided almost none information (is like going to the doctor and say “I feel bad”).
Even without information I told you “is the heap”. Now I will told you something more: a debug vm will not help you much because you are running out of resources *in the HEAP*.

try expanding memory and monitoring memory consumption to see how it goes.
try forcing free of resources in your visualisations or anything “FFI Related”.

cheers,
Esteban

ps: And yes, we need to update the “debug vm build” info in the instructions, but is just affecting on line or so :)
pps: And we also could provide some debug vms for this cases. I cannot schedule the time now for doing the jobs, but I will put it in my TODO list.

---> Save our in-boxes! http://emailcharter.org <---

Johan Fabry - http://pleiad.cl/~jfabry
PLEIAD and RyCh labs - Computer Science Department (DCC) - University of Chile

Mariano Martinez Peck

Re: VM crash on Ubuntu 14.04

In reply to this post by Ben Coman

On Sat, Oct 31, 2015 at 11:27 PM, Ben Coman <[hidden email]> wrote:

On Fri, Oct 30, 2015 at 2:03 AM, Johan Fabry <[hidden email]> wrote:
>
> OK, back with access to the Ubuntu machine, I reproduced the crash when
> running under gdb (reproducing it is never an issue, finding the minimal
> case is the issue). See below for gdb output. But my vm has no debug
> information compiled, so it is not really useful. Can I download a vm with
> debug info compiled from somewhere? I would prefer to avoid having to
> download the sources and compile et cetera …

Why not give it a go? :) I found it dead simple to compile the VM for
the first time following instructions at...
[1] https://github.com/pharo-project/pharo-vm

This was on OSX and the only problem I had was _not_ following the
instructions and using XCode 10.9 instead of 10.6.
I can't speak for Ubuntu but its the reference Unix platform. I guess
you'll get better support getting started with the standard
instructions (since we'd like them "perfect" and more people will be
able to replicate a problem with these than replicate your unique
problem)

One thing though, could someone update [1] to describe how to get a
debug VM, since that must be a common reason someone wants to compile
their own VM for the first time. I hunted around for some info but
could only find tips from a few years ago and I'm not sure if they
still apply

Debug a VM (by Mariano)
https://marianopeck.wordpress.com/2011/04/10/building-the-vm-from-scratch-using-git-and-cmakevmmaker/
https://marianopeck.wordpress.com/2011/04/16/building-the-vm-second-part/

And you forgot the most important one: https://marianopeck.wordpress.com/2011/04/23/how-to-debug-the-vm/ :)

I don't remember who said it in this thread, but I also suggested a couple of years ago, to provide a Pharo Debug VM right from the CI so that people can hunt this kind of problems. Of course, we always had too busy agendas and nobody could do it. But I still think it will be very helpful to provide a VM binary directly built in debug.

https://vimeo.com/22485382 (PharoCast)

Debugging assembly in Pharo VM with GDB (by Melkyades)
http://melkyades.blogspot.com.au/2013/07/debugging-assembly-in-pharo-vm-with-gdb.html

cheers -ben

>
> Once I have such a VM I will make some time to further investigate, and
> report results.
>
> Program received signal SIGSEGV, Segmentation fault.
> 0xb8c2bc31 in ?? ()
> (gdb) bt
> #0 0xb8c2bc31 in ?? ()
> #1 0x080fc9f2 in primitiveNativeCall ()
> #2 0xb4fba770 in ?? ()
> #3 0xb503b05e in ?? ()
> #4 0xb503afcb in ?? ()
> #5 0xb5011abd in ?? ()
> #6 0xb4fba5c0 in ?? ()
> (gdb)
>
> On Oct 27, 2015, at 19:09, Nicolai Hess <[hidden email]> wrote:
>
>
>
> 2015-10-26 15:03 GMT+01:00 Johan Fabry <[hidden email]>:
>>
>> Hi Nicolai,
>>
>> thanks for following up on this.
>>
>> I am in the process of determining what causes the crash. I fear that to
>> reproduce the problem you will need to have ROS installed, I have not yet
>> been able to reproduce it without ROS running. I do not want to inflict the
>> installation of ROS on you without being 100% sure.
>>
>> I am using Roassal because this is for Live Robot Programming
>> (http://pleiad.cl/LRP) which uses a dynamic visualization of the running
>> code. To reproduce the bug (until now) I need to develop code in LRP when
>> using ROS, and then it happens randomly. I realize that this is too much to
>> ask for an outsider to reproduce the bug (I did not expect anybody to
>> download and install PhaROS to try to reproduce, thanks for that!!).
>>
>> Can you inform me how I can get you more useful debug info to you? I will
>> keep trying to find minimal steps to reproduce in the mean time.
>
>
> No, the best we can hope for is a crash when it is running from debugger,
> you can start the vm with a debugger or attach the debugger to a running
> process. If we are lucky, the debugger will show a stacktrace.
>
>>
>>
>> On Oct 24, 2015, at 19:45, Nicolai Hess <[hidden email]> wrote:
>>
>> Can you provide the image file.
>> What exactly runs in the image (does it depend on ROS or
>> does it crash even without it). For what do you
>> use Roassal in this environment.
>> Can you reproduce the crash with a clean image (and maybe loading
>> some package - without all of the ROS-stuff?
>> (I just followed the installation guide for PhaROS, but I have no idea
>> how to go from here to do anything to reproduce the crash).
>>
>>
>>
>> 2015-10-24 21:32 GMT+02:00 Johan Fabry <[hidden email]>:
>>>
>>>
>>> Ben, thanks for replying but since no VM guys are following up on this,
>>> apparently, it does not make much sense for me to go this way.
>>>
>>> Guys, am I to assume there is not help for me on this topic?
>>>
>>> > On Oct 23, 2015, at 11:03, Ben Coman <[hidden email]> wrote:
>>> >
>>> > On Thu, Oct 22, 2015 at 2:25 AM, Johan Fabry <[hidden email]>
>>> > wrote:
>>> >> Hi all,
>>> >>
>>> >> I am having some unpleasant experiences on Ubuntu 14.04 (experimenting
>>> >> with Live Robot Programming on PhaROS). The VM crashes after a random amount
>>> >> of time (< 25 minutes), with no clear sequence of steps on how to reproduce
>>> >> the crash. I am using Pharo 4 (Pharo 40622 as installed by PhaROS) + Roassal
>>> >> which required an install of libcairo2:i386 . VM version details below.
>>> >>
>>> >> There is no printout on stdout, and the debug.log does not contain
>>> >> recent entries (timestamp is always some minutes before the actual crash
>>> >> happens).
>>> >>
>>> >> Is this a known problem? If so, how can I fix it, and if not how can I
>>> >> provide more debugging info?
>>> >>
>>> >> Thanks in advance!
>>> >
>>> > I'm not much help since I haven't done these myself, but just some
>>> > ideas (maybe someone can add more details)
>>> > * compile and run a debug vm
>>> > * trace all function calls, http://tinyurl.com/gdb-trace-all
>>> >
>>>
>>>
>>>
>>> ---> Save our in-boxes! http://emailcharter.org <---
>>>
>>> Johan Fabry - http://pleiad.cl/~jfabry
>>> PLEIAD and RyCh labs - Computer Science Department (DCC) - University
>>> of Chile
>>>
>>>
>>
>>
>>
>>
>> ---> Save our in-boxes! http://emailcharter.org <---
>>
>> Johan Fabry - http://pleiad.cl/~jfabry
>> PLEIAD and RyCh labs - Computer Science Department (DCC) - University
>> of Chile
>
>
>
>
> ---> Save our in-boxes! http://emailcharter.org <---
>
> Johan Fabry - http://pleiad.cl/~jfabry
> PLEIAD and RyCh labs - Computer Science Department (DCC) - University of
> Chile
>

Mariano
http://marianopeck.wordpress.com