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! vm version: 3.9-7 #1 Thu May 15 18:29:30 CEST 2014 gcc 4.6.3 [Production ITHB VM] NBCoInterpreter NativeBoost-CogPlugin-GuillermoPolito.19 uuid: acc98e51-2fba-484 1-a965-2975997bba66 May 15 2014 NBCogit NativeBoost-CogPlugin-GuillermoPolito.19 uuid: acc98e51-2fba-4841-a965-2 975997bba66 May 15 2014 https://github.com/pharo-project/pharo-vm.git Commit: ed4a4f59208968a21d82fd2406 f75c2c4de558b2 Date: 2014-05-15 18:23:04 +0200 By: Esteban Lorenzano <estebanlm@ gmail.com> Jenkins build #14826 Linux pharo-linux 3.2.0-31-generic-pae #50-Ubuntu SMP Fri Sep 7 16:39:45 UTC 201 2 i686 i686 i386 GNU/Linux plugin path: /home/jfabry/catkin_ws/src/pharo/vm/ [default: /home/jfabry/catkin_ ws/src/pharo/vm/] ---> Save our in-boxes! http://emailcharter.org <--- Johan Fabry - http://pleiad.cl/~jfabry PLEIAD and RyCh labs - Computer Science Department (DCC) - University of Chile
Bump. Nobody can at least tell me how to get more debug info?
On Oct 21, 2015, at 15:25, Johan Fabry <jfabry@dcc.uchile.cl> 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!
vm version: 3.9-7 #1 Thu May 15 18:29:30 CEST 2014 gcc 4.6.3 [Production ITHB VM] NBCoInterpreter NativeBoost-CogPlugin-GuillermoPolito.19 uuid: acc98e51-2fba-484 1-a965-2975997bba66 May 15 2014 NBCogit NativeBoost-CogPlugin-GuillermoPolito.19 uuid: acc98e51-2fba-4841-a965-2 975997bba66 May 15 2014 https://github.com/pharo-project/pharo-vm.git Commit: ed4a4f59208968a21d82fd2406 f75c2c4de558b2 Date: 2014-05-15 18:23:04 +0200 By: Esteban Lorenzano <estebanlm@ gmail.com> Jenkins build #14826 Linux pharo-linux 3.2.0-31-generic-pae #50-Ubuntu SMP Fri Sep 7 16:39:45 UTC 201 2 i686 i686 i386 GNU/Linux plugin path: /home/jfabry/catkin_ws/src/pharo/vm/ [default: /home/jfabry/catkin_ ws/src/pharo/vm/]
---> 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
is there a crash,dmp?
On 22 Oct 2015, at 16:37, Johan Fabry <jfabry@dcc.uchile.cl> wrote:
Bump.
Nobody can at least tell me how to get more debug info?
On Oct 21, 2015, at 15:25, Johan Fabry <jfabry@dcc.uchile.cl> 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!
vm version: 3.9-7 #1 Thu May 15 18:29:30 CEST 2014 gcc 4.6.3 [Production ITHB VM] NBCoInterpreter NativeBoost-CogPlugin-GuillermoPolito.19 uuid: acc98e51-2fba-484 1-a965-2975997bba66 May 15 2014 NBCogit NativeBoost-CogPlugin-GuillermoPolito.19 uuid: acc98e51-2fba-4841-a965-2 975997bba66 May 15 2014 https://github.com/pharo-project/pharo-vm.git Commit: ed4a4f59208968a21d82fd2406 f75c2c4de558b2 Date: 2014-05-15 18:23:04 +0200 By: Esteban Lorenzano <estebanlm@ gmail.com> Jenkins build #14826 Linux pharo-linux 3.2.0-31-generic-pae #50-Ubuntu SMP Fri Sep 7 16:39:45 UTC 201 2 i686 i686 i386 GNU/Linux plugin path: /home/jfabry/catkin_ws/src/pharo/vm/ [default: /home/jfabry/catkin_ ws/src/pharo/vm/]
---> 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
No, I cannot find any file named crash.dmp or anything containing the word crash in my home dir (using find | grep crash )
On Oct 22, 2015, at 11:40, Esteban Lorenzano <estebanlm@gmail.com> wrote:
is there a crash,dmp?
On 22 Oct 2015, at 16:37, Johan Fabry <jfabry@dcc.uchile.cl> wrote:
Bump.
Nobody can at least tell me how to get more debug info?
On Oct 21, 2015, at 15:25, Johan Fabry <jfabry@dcc.uchile.cl> 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!
vm version: 3.9-7 #1 Thu May 15 18:29:30 CEST 2014 gcc 4.6.3 [Production ITHB VM] NBCoInterpreter NativeBoost-CogPlugin-GuillermoPolito.19 uuid: acc98e51-2fba-484 1-a965-2975997bba66 May 15 2014 NBCogit NativeBoost-CogPlugin-GuillermoPolito.19 uuid: acc98e51-2fba-4841-a965-2 975997bba66 May 15 2014 https://github.com/pharo-project/pharo-vm.git Commit: ed4a4f59208968a21d82fd2406 f75c2c4de558b2 Date: 2014-05-15 18:23:04 +0200 By: Esteban Lorenzano <estebanlm@ gmail.com> Jenkins build #14826 Linux pharo-linux 3.2.0-31-generic-pae #50-Ubuntu SMP Fri Sep 7 16:39:45 UTC 201 2 i686 i686 i386 GNU/Linux plugin path: /home/jfabry/catkin_ws/src/pharo/vm/ [default: /home/jfabry/catkin_ ws/src/pharo/vm/]
---> 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
at the side of the binary of the vm?
On 22 Oct 2015, at 16:53, Johan Fabry <jfabry@dcc.uchile.cl> wrote:
No, I cannot find any file named crash.dmp or anything containing the word crash in my home dir (using find | grep crash )
On Oct 22, 2015, at 11:40, Esteban Lorenzano <estebanlm@gmail.com> wrote:
is there a crash,dmp?
On 22 Oct 2015, at 16:37, Johan Fabry <jfabry@dcc.uchile.cl> wrote:
Bump.
Nobody can at least tell me how to get more debug info?
On Oct 21, 2015, at 15:25, Johan Fabry <jfabry@dcc.uchile.cl> 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!
vm version: 3.9-7 #1 Thu May 15 18:29:30 CEST 2014 gcc 4.6.3 [Production ITHB VM] NBCoInterpreter NativeBoost-CogPlugin-GuillermoPolito.19 uuid: acc98e51-2fba-484 1-a965-2975997bba66 May 15 2014 NBCogit NativeBoost-CogPlugin-GuillermoPolito.19 uuid: acc98e51-2fba-4841-a965-2 975997bba66 May 15 2014 https://github.com/pharo-project/pharo-vm.git Commit: ed4a4f59208968a21d82fd2406 f75c2c4de558b2 Date: 2014-05-15 18:23:04 +0200 By: Esteban Lorenzano <estebanlm@ gmail.com> Jenkins build #14826 Linux pharo-linux 3.2.0-31-generic-pae #50-Ubuntu SMP Fri Sep 7 16:39:45 UTC 201 2 i686 i686 i386 GNU/Linux plugin path: /home/jfabry/catkin_ws/src/pharo/vm/ [default: /home/jfabry/catkin_ ws/src/pharo/vm/]
---> 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
No, there is no crash file there (the vm directory is also in my home dir) and there is nothing new in the vm directory since I installed it
On Oct 22, 2015, at 11:57, Esteban Lorenzano <estebanlm@gmail.com> wrote:
at the side of the binary of the vm?
On 22 Oct 2015, at 16:53, Johan Fabry <jfabry@dcc.uchile.cl> wrote:
No, I cannot find any file named crash.dmp or anything containing the word crash in my home dir (using find | grep crash )
On Oct 22, 2015, at 11:40, Esteban Lorenzano <estebanlm@gmail.com> wrote:
is there a crash,dmp?
On 22 Oct 2015, at 16:37, Johan Fabry <jfabry@dcc.uchile.cl> wrote:
Bump.
Nobody can at least tell me how to get more debug info?
On Oct 21, 2015, at 15:25, Johan Fabry <jfabry@dcc.uchile.cl> 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!
vm version: 3.9-7 #1 Thu May 15 18:29:30 CEST 2014 gcc 4.6.3 [Production ITHB VM] NBCoInterpreter NativeBoost-CogPlugin-GuillermoPolito.19 uuid: acc98e51-2fba-484 1-a965-2975997bba66 May 15 2014 NBCogit NativeBoost-CogPlugin-GuillermoPolito.19 uuid: acc98e51-2fba-4841-a965-2 975997bba66 May 15 2014 https://github.com/pharo-project/pharo-vm.git Commit: ed4a4f59208968a21d82fd2406 f75c2c4de558b2 Date: 2014-05-15 18:23:04 +0200 By: Esteban Lorenzano <estebanlm@ gmail.com> Jenkins build #14826 Linux pharo-linux 3.2.0-31-generic-pae #50-Ubuntu SMP Fri Sep 7 16:39:45 UTC 201 2 i686 i686 i386 GNU/Linux plugin path: /home/jfabry/catkin_ws/src/pharo/vm/ [default: /home/jfabry/catkin_ ws/src/pharo/vm/]
---> 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
---> Save our in-boxes! http://emailcharter.org <--- Johan Fabry - http://pleiad.cl/~jfabry PLEIAD and RyCh labs - Computer Science Department (DCC) - University of Chile
On Thu, Oct 22, 2015 at 2:25 AM, Johan Fabry <jfabry@dcc.uchile.cl> 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 cheers -ben
vm version: 3.9-7 #1 Thu May 15 18:29:30 CEST 2014 gcc 4.6.3 [Production ITHB VM] NBCoInterpreter NativeBoost-CogPlugin-GuillermoPolito.19 uuid: acc98e51-2fba-484 1-a965-2975997bba66 May 15 2014 NBCogit NativeBoost-CogPlugin-GuillermoPolito.19 uuid: acc98e51-2fba-4841-a965-2 975997bba66 May 15 2014 https://github.com/pharo-project/pharo-vm.git Commit: ed4a4f59208968a21d82fd2406 f75c2c4de558b2 Date: 2014-05-15 18:23:04 +0200 By: Esteban Lorenzano <estebanlm@ gmail.com> Jenkins build #14826 Linux pharo-linux 3.2.0-31-generic-pae #50-Ubuntu SMP Fri Sep 7 16:39:45 UTC 201 2 i686 i686 i386 GNU/Linux plugin path: /home/jfabry/catkin_ws/src/pharo/vm/ [default: /home/jfabry/catkin_ ws/src/pharo/vm/]
---> Save our in-boxes! http://emailcharter.org <---
Johan Fabry - http://pleiad.cl/~jfabry PLEIAD and RyCh labs - Computer Science Department (DCC) - University of Chile
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 <btc@openInWorld.com> wrote:
On Thu, Oct 22, 2015 at 2:25 AM, Johan Fabry <jfabry@dcc.uchile.cl> 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
Posting to Pharos-dev or Vm Dev may find you more assistance. My suggestions would be: a) upgrade to Pharo 5 and b) run in gdb so we all can be better informed about the issue you are seeing. Is PhaROS doing low level calls? --- robert
On Oct 24, 2015, at 3:32 PM, Johan Fabry <jfabry@dcc.uchile.cl> 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.
Guys, am I to assume there is not help for me on this topic?
On Oct 23, 2015, at 11:03, Ben Coman <btc@openInWorld.com> wrote:
On Thu, Oct 22, 2015 at 2:25 AM, Johan Fabry <jfabry@dcc.uchile.cl> 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
Hi Robert, thanks for the hints. Unfortunately running in Pharo 5 is not feasible. PhaROS does not do any low-level calls as far as I am aware (I did not implement it, Iâm just using it). I will try to run it in gdb as soon as I can find a reliable way to reproduce the crash.
On Oct 24, 2015, at 16:52, Robert Withers <robert.w.withers@gmail.com> wrote:
Posting to Pharos-dev or Vm Dev may find you more assistance.
My suggestions would be: a) upgrade to Pharo 5 and b) run in gdb so we all can be better informed about the issue you are seeing. Is PhaROS doing low level calls?
--- robert
On Oct 24, 2015, at 3:32 PM, Johan Fabry <jfabry@dcc.uchile.cl> 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.
Guys, am I to assume there is not help for me on this topic?
On Oct 23, 2015, at 11:03, Ben Coman <btc@openInWorld.com> wrote:
On Thu, Oct 22, 2015 at 2:25 AM, Johan Fabry <jfabry@dcc.uchile.cl> 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
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 <jfabry@dcc.uchile.cl>:
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 <btc@openInWorld.com> wrote:
On Thu, Oct 22, 2015 at 2:25 AM, Johan Fabry <jfabry@dcc.uchile.cl> 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
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 <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.
On Oct 24, 2015, at 19:45, Nicolai Hess <nicolaihess@gmail.com> 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 <jfabry@dcc.uchile.cl <mailto:jfabry@dcc.uchile.cl>>:
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 <btc@openInWorld.com> wrote:
On Thu, Oct 22, 2015 at 2:25 AM, Johan Fabry <jfabry@dcc.uchile.cl <mailto:jfabry@dcc.uchile.cl>> 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 <http://tinyurl.com/gdb-trace-all>
---> Save our in-boxes! http://emailcharter.org <http://emailcharter.org/> <---
Johan Fabry - http://pleiad.cl/~jfabry <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
2015-10-26 15:03 GMT+01:00 Johan Fabry <jfabry@dcc.uchile.cl>:
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 <nicolaihess@gmail.com> 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 <jfabry@dcc.uchile.cl>:
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 <btc@openInWorld.com> wrote:
On Thu, Oct 22, 2015 at 2:25 AM, Johan Fabry <jfabry@dcc.uchile.cl> 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
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 ⦠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 <nicolaihess@gmail.com> wrote:
2015-10-26 15:03 GMT+01:00 Johan Fabry <jfabry@dcc.uchile.cl <mailto:jfabry@dcc.uchile.cl>>: 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 <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 <nicolaihess@gmail.com <mailto:nicolaihess@gmail.com>> 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 <jfabry@dcc.uchile.cl <mailto:jfabry@dcc.uchile.cl>>:
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 <btc@openInWorld.com <mailto:btc@openInWorld.com>> wrote:
On Thu, Oct 22, 2015 at 2:25 AM, Johan Fabry <jfabry@dcc.uchile.cl <mailto:jfabry@dcc.uchile.cl>> 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 <http://tinyurl.com/gdb-trace-all>
---> Save our in-boxes! http://emailcharter.org <http://emailcharter.org/> <---
Johan Fabry - http://pleiad.cl/~jfabry <http://pleiad.cl/~jfabry> PLEIAD and RyCh labs - Computer Science Department (DCC) - University of Chile
---> Save our in-boxes! http://emailcharter.org <http://emailcharter.org/> <---
Johan Fabry - http://pleiad.cl/~jfabry <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
you can type p (void)printCallStack() then you will have the active stack when crash happened. Is often a lot more useful than the trace of the vm. Esteban
On 29 Oct 2015, at 19:03, Johan Fabry <jfabry@dcc.uchile.cl> 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 â¦
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 <nicolaihess@gmail.com <mailto:nicolaihess@gmail.com>> wrote:
2015-10-26 15:03 GMT+01:00 Johan Fabry <jfabry@dcc.uchile.cl <mailto:jfabry@dcc.uchile.cl>>: 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 <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 <nicolaihess@gmail.com <mailto:nicolaihess@gmail.com>> 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 <jfabry@dcc.uchile.cl <mailto:jfabry@dcc.uchile.cl>>:
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 <btc@openInWorld.com <mailto:btc@openInWorld.com>> wrote:
On Thu, Oct 22, 2015 at 2:25 AM, Johan Fabry <jfabry@dcc.uchile.cl <mailto:jfabry@dcc.uchile.cl>> 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 <http://tinyurl.com/gdb-trace-all>
---> Save our in-boxes! http://emailcharter.org <http://emailcharter.org/> <---
Johan Fabry - http://pleiad.cl/~jfabry <http://pleiad.cl/~jfabry> PLEIAD and RyCh labs - Computer Science Department (DCC) - University of Chile
---> Save our in-boxes! http://emailcharter.org <http://emailcharter.org/> <---
Johan Fabry - http://pleiad.cl/~jfabry <http://pleiad.cl/~jfabry> PLEIAD and RyCh labs - Computer Science Department (DCC) - University of Chile
---> Save our in-boxes! http://emailcharter.org <http://emailcharter.org/> <---
Johan Fabry - http://pleiad.cl/~jfabry <http://pleiad.cl/~jfabry> PLEIAD and RyCh labs - Computer Science Department (DCC) - University of Chile
More bad luck Iâm afraid. What can I do next? Program received signal SIGSEGV, Segmentation fault. 0xb8c0b92d in ?? () (gdb) p (void)printCallStack() Cannot access memory at address 0xffffffff (gdb)
On Oct 30, 2015, at 08:11, Esteban Lorenzano <estebanlm@gmail.com> wrote:
you can type
p (void)printCallStack()
then you will have the active stack when crash happened. Is often a lot more useful than the trace of the vm.
Esteban
On 29 Oct 2015, at 19:03, Johan Fabry <jfabry@dcc.uchile.cl <mailto:jfabry@dcc.uchile.cl>> 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 â¦
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)
---> Save our in-boxes! http://emailcharter.org <--- Johan Fabry - http://pleiad.cl/~jfabry PLEIAD and RyCh labs - Computer Science Department (DCC) - University of Chile
not so bad⦠that actually means that you are running out of heap, badly :P and since I see a primitiveNativeCall there, most probably your (athens?) program is leaking somewhere. Esteban
On 30 Oct 2015, at 18:01, Johan Fabry <jfabry@dcc.uchile.cl> wrote:
More bad luck Iâm afraid. What can I do next?
Program received signal SIGSEGV, Segmentation fault. 0xb8c0b92d in ?? () (gdb) p (void)printCallStack() Cannot access memory at address 0xffffffff (gdb)
On Oct 30, 2015, at 08:11, Esteban Lorenzano <estebanlm@gmail.com <mailto:estebanlm@gmail.com>> wrote:
you can type
p (void)printCallStack()
then you will have the active stack when crash happened. Is often a lot more useful than the trace of the vm.
Esteban
On 29 Oct 2015, at 19:03, Johan Fabry <jfabry@dcc.uchile.cl <mailto:jfabry@dcc.uchile.cl>> 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 â¦
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)
---> Save our in-boxes! http://emailcharter.org <http://emailcharter.org/> <---
Johan Fabry - http://pleiad.cl/~jfabry <http://pleiad.cl/~jfabry> PLEIAD and RyCh labs - Computer Science Department (DCC) - University of Chile
Ah those wonderful memory leaks ⦠:-/ I will try to narrow down the possible source, but that is not going to be easy ⦠Itâs really a very specific setup that always crashes on me, so It must be a freaky combination of factors that triggers the issue. Running a Roassal visualization certainly is needed to crash, but apparently itâs not the only thing. I will keep trying to remove elements from the setup to see what the required combination is.
On Oct 31, 2015, at 07:38, Esteban Lorenzano <estebanlm@gmail.com> wrote:
not so bad⦠that actually means that you are running out of heap, badly :P and since I see a primitiveNativeCall there, most probably your (athens?) program is leaking somewhere.
Esteban
On 30 Oct 2015, at 18:01, Johan Fabry <jfabry@dcc.uchile.cl <mailto:jfabry@dcc.uchile.cl>> wrote:
More bad luck Iâm afraid. What can I do next?
Program received signal SIGSEGV, Segmentation fault. 0xb8c0b92d in ?? () (gdb) p (void)printCallStack() Cannot access memory at address 0xffffffff (gdb)
On Oct 30, 2015, at 08:11, Esteban Lorenzano <estebanlm@gmail.com <mailto:estebanlm@gmail.com>> wrote:
you can type
p (void)printCallStack()
then you will have the active stack when crash happened. Is often a lot more useful than the trace of the vm.
Esteban
On 29 Oct 2015, at 19:03, Johan Fabry <jfabry@dcc.uchile.cl <mailto:jfabry@dcc.uchile.cl>> 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 â¦
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)
---> Save our in-boxes! http://emailcharter.org <http://emailcharter.org/> <---
Johan Fabry - http://pleiad.cl/~jfabry <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
On Fri, Oct 30, 2015 at 2:03 AM, Johan Fabry <jfabry@dcc.uchile.cl> 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-us... 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... 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 <nicolaihess@gmail.com> wrote:
2015-10-26 15:03 GMT+01:00 Johan Fabry <jfabry@dcc.uchile.cl>:
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 <nicolaihess@gmail.com> 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 <jfabry@dcc.uchile.cl>:
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 <btc@openInWorld.com> wrote:
On Thu, Oct 22, 2015 at 2:25 AM, Johan Fabry <jfabry@dcc.uchile.cl> 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
On Sat, Oct 31, 2015 at 11:27 PM, Ben Coman <btc@openinworld.com> wrote: > On Fri, Oct 30, 2015 at 2:03 AM, Johan Fabry <jfabry@dcc.uchile.cl> 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 <nicolaihess@gmail.com> wrote: > > > > > > > > 2015-10-26 15:03 GMT+01:00 Johan Fabry <jfabry@dcc.uchile.cl>: > >> > >> 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 <nicolaihess@gmail.com> 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 <jfabry@dcc.uchile.cl>: > >>> > >>> > >>> 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 <btc@openInWorld.com> wrote: > >>> > > >>> > On Thu, Oct 22, 2015 at 2:25 AM, Johan Fabry <jfabry@dcc.uchile.cl> > >>> > 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
Why do you say that johan? Everybody is busy and has its own agenda. I'm sure that esteban would love to have the time to just wait for helping people. This is not the case and the dragons he is fighting against are quite large and venomous. So the suggestion of Ben is good because else I do not see how people can help you. Stef Le 24/10/15 12:32, Johan Fabry a écrit : > 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 <btc@openInWorld.com> wrote: >> >> On Thu, Oct 22, 2015 at 2:25 AM, Johan Fabry <jfabry@dcc.uchile.cl> 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 > > >
Hi Johan, Perhaps I can try to help you debugging with gdb. Are you using a 32 bits or 64 bits Ubuntu ? We should start by building a debug Pharo VM. Do you have some time during Monday or Wednesday in your office?. Greetings, Ronie 2015-10-31 22:00 GMT-03:00 stepharo <stepharo@free.fr>:
Why do you say that johan? Everybody is busy and has its own agenda. I'm sure that esteban would love to have the time to just wait for helping people. This is not the case and the dragons he is fighting against are quite large and venomous. So the suggestion of Ben is good because else I do not see how people can help you.
Stef
Le 24/10/15 12:32, Johan Fabry a écrit :
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 <btc@openInWorld.com> wrote:
On Thu, Oct 22, 2015 at 2:25 AM, Johan Fabry <jfabry@dcc.uchile.cl> 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
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.
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 <estebanlm@gmail.com> 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
participants (8)
-
Ben Coman -
Esteban Lorenzano -
Johan Fabry -
Mariano Martinez Peck -
Nicolai Hess -
Robert Withers -
Ronie Salgado -
stepharo