[Fluxus] zsh: abort

Tue May 25 10:54:23 PDT 2010

Hi Dave,

Below story short: on a HP laptop and on a HP desktop fluxus crashes on my DELL Latitude d620 all works fine.

1)	I created an image CD via puredyne.
 a.	Via: NL, Amsterdam, primary server: GOTO10
 b.	Version: puredyne-911-carrot_and_coriander-CD-i386.iso (26-Mar-2010 23:08 693M)
 c.	Nothing else extra installed, only “play” the CD
2)	First I just loaded the cd (created a virtual machine, ran everything via the CD)
 a.	The error occurred once in while on version 0.16
 b.	The error occurred more on 0.17 (but same error on both versions)
3)	I have a copy of that puredyne image for my desktop HP compaq dc 7800 (512mb) at work, standard graphicCard.
 a.	On this one the error occurs just the same as on my HP laptop at home.
  i.	On the HP laptop I installed the puredyne CD (not virtual mavhine but really installed) because we figured out that the v0.17 also needed some updates. I thought that if you run this only via CD the upgrading was temporary (each time you start you need to update/upgrade or make a new image after updating). If it is installed you actally save the upgrades.
  ii.	After I updated/upgraded Fluxus on my laptop, the error still occurs
  iii.	I took my DELL laptop and I cannot reproduce the error, I can move my cube with my mouse as fast and as long as I want, no error occurs.
4)	On the desktop (with CD) and on the laptop (imaged) I open fluxus by typing fluxus in command prompt. (that is called: urxvt)
 a.	Then I see Fluxus welcome message.
 b.	Then I press ctrl-1 to get in a new scratch pad.
 c.	There I load or write a script.
 d.	I press F5, it runs smooth until I manipulate it with my mouse (rotate, give other angel, move it, change size)…
 e.	Manipulate with mouse is what causing the crash.
  i.	Sometimes the screen freezes, sometimes I get thrown out the scratch pad.
  ii.	Sometimes I can play with fluxus a few hours, and all goes well and all of a sudden I move an object with my mouse and there the error goes again.
  iii.	The same I do on the DELL (latitude D620) and the error does not occurs.

It looks like I have it on HP machines and not on my dell.
Are there other HP fluxus users? I cannot imagine that I am the only HP owner who runs fluxus 
But it is both on HP clients that I see the error on my DELL all works fine.

I wish I could make it work on my HP too, the DELL is for my mails and used by my girlfriend, but I will create my stuff on a DELL from now on.

Best regards,
Elmer

-----Original Message-----
From: Dave Griffiths [mailto:dave at pawfal.org] 
Sent: dinsdag 25 mei 2010 10:16
To: Elmer & Maddy
Cc: 'gabor papp'; fluxus at lists.pawfal.org
Subject: Re: [Fluxus] zsh: abort

Hi Elmer,

This is quite worrying as it looks like it's a crash that we haven't found yet, but you're the only one getting it at the moment! 

Just to check - when you boot puredyne on your machine from CD you still get the crash? If you could try it on another machine it would be interesting to know if you get it there too.

Could you give us some detailed steps that reproduce the crash, for
example:

* starting fluxus from the command line
* going to a workspace with ctrl-1
* pressing ctrl-l to load the file
* pressing F5, moving the mouse around.

It may help us to identify some pattern that is causing it that we aren't testing somehow.

cheers,

dave

On Mon, 2010-05-24 at 14:09 +0200, Elmer & Maddy wrote:
> If anyone ever hear about a solution for this thrown out/crash/error...please help, very annoying.
> 
> Cheers,
> Elmer
> 
> -----Original Message-----
> From: Elmer & Maddy [mailto:FA701138 at skynet.be]
> Sent: zondag 16 mei 2010 10:03
> To: 'Elmer & Maddy'; 'gabor papp'
> Cc: fluxus at lists.pawfal.org
> Subject: RE: [Fluxus] zsh: abort
> 
> Darn, I shouted victory too soon:
> Error is here again:
> 
> Program received signal SIGABRT, Aborted.
> 0x00194422 in __kernel_vsyscall ()
> (gdb) bt
> #0  0x00194422 in __kernel_vsyscall ()
> #1  0x00ada4d1 in raise () from /lib/tls/i686/cmov/libc.so.6
> #2  0x00add932 in abort () from /lib/tls/i686/cmov/libc.so.6
> #3  0x08233015 in fault_handler ()
> #4  <signal handler called>
> #5  0x00000001 in ?? ()
> #6  0x08235581 in ?? ()
> #7  0x0822f5ef in ?? ()
> #8  0x0822f86f in GC_malloc_one_tagged ()
> #9  0x0822f6d4 in ?? ()
> #10 0x0822f960 in GC_malloc_one_small_tagged ()
> #11 0x080e144d in scheme_make_hash_table ()
> #12 0x081e2c61 in ?? ()
> #13 0x081e2f80 in scheme_datum_to_syntax ()
> #14 0x081e401b in ?? ()
> #15 0x006c2f59 in ?? ()
> #16 0x080b12aa in scheme_do_eval ()
> #17 0x080cfdc6 in ?? ()
> #18 0x080cf888 in scheme_top_level_do_worker ()
> #19 0x080cff54 in scheme_apply_with_dynamic_state () #20 0x080d14de in 
> scheme_apply_macro ()
> #21 0x080a644c in ?? ()
> #22 0x080a855f in ?? ()
> #23 0x080ab2c5 in scheme_compile_expr ()
> #24 0x080a58da in ?? ()
> #25 0x080cf888 in scheme_top_level_do_worker ()
> #26 0x080cf565 in scheme_top_level_do ()
> #27 0x080a5cbe in ?? ()
> #28 0x080b472b in scheme_default_compile_handler ()
> #29 0x080b08ac in scheme_do_eval ()
> #30 0x080cfdc6 in ?? ()
> #31 0x080cf888 in scheme_top_level_do_worker ()
> #32 0x080cf565 in scheme_top_level_do ()
> #33 0x080cfe27 in ?? ()
> #34 0x080cfe58 in scheme_apply ()
> #35 0x080a4bfa in ?? ()
> #36 0x080a580c in ?? ()
> #37 0x080cf888 in scheme_top_level_do_worker ()
> #38 0x080cf565 in scheme_top_level_do ()
> #39 0x080a5cbe in ?? ()
> #40 0x080a5d31 in scheme_compile_for_eval ()
> #41 0x080b2f26 in scheme_eval_multi ()
> #42 0x080b640b in ?? ()
> #43 0x080b6577 in scheme_eval_string_all ()
> #44 0x0806ef4d in fluxus::Interpreter::Interpret(std::basic_string<wchar_t, std::char_traits<wchar_t>, std::allocator<wchar_t> > const&, Scheme_Object**, bool)    ()
> #45 0x0807ab6b in MotionCallback(int, int) ()
> #46 0x002aa0c4 in glutMainLoopEvent () from /usr/lib/libglut.so.3
> #47 0x002aa3dd in glutMainLoop () from /usr/lib/libglut.so.3
> #48 0x0807c4dc in run(void*) ()
> #49 0x0807d00f in scheme_main_stack_setup () #50 0x0807a551 in main ()
> (gdb)
> 
> -----Original Message-----
> From: fluxus-bounces at lists.pawfal.org 
> [mailto:fluxus-bounces at lists.pawfal.org] On Behalf Of Elmer & Maddy
> Sent: zaterdag 15 mei 2010 19:48
> To: 'gabor papp'
> Cc: fluxus at lists.pawfal.org
> Subject: Re: [Fluxus] zsh: abort
> 
> Hi,
> 
> @ Gabor: yes, I ran .gdbinit with the lines in it.	
> @ Dave: yes, I did the apt-get upgrade and all is up to date now. 
> 	(help "hint")==> displays with the "Function not found, did you mean one of these?"
> 
> I think I found the problem: Everything is up to date now. But I made some stuff I use frequently (light, some cubes and rows, practical stuff) Instead of typing that, I saved it, I load it and copy paste it when I wanna use it. But those where written on 0.16 and on not upgraded 0.17.
> 
> If I write something totally new in my upgraded 0.17 fluxus, no crashes appear.
> When I use some of my pre-scripted stuff (wrote on 0.16 and on not updated 0.17) I get a crash.
> 
> I will keep an eye on it and post it when it happens again, but I think it is solved.
> 
> Thank you for helping me out here!
> 
> Br,
> Elmer
> 
> 
> 
> -----Original Message-----
> From: gabor papp [mailto:gabor.lists at mndl.hu]
> Sent: zaterdag 15 mei 2010 16:49
> To: Elmer & Maddy
> Cc: fluxus at lists.pawfal.org
> Subject: Re: [Fluxus] zsh: abort
> 
> > I hope anyone can filter out via this what is wrong, is it my drivers? 
> > Is it my laptop?? (is it me?)
> it seems it is crashing inside plt scheme. just to make sure, did you write a .gdbinit file before running gdb with these lines in it?
> 
> handle SIGSEGV nostop noprint
> handle SIG33 nostop noprint pass
> handle SIG32 nostop noprint pass
> 
> gabor
> 