[GEM-dev] [ pd-gem-Bugs-3313799 ] example 04.pix/26.framebuffer_readback crash

SourceForge.net noreply at sourceforge.net
Wed Jun 8 22:04:21 CEST 2011


Bugs item #3313799, was opened at 2011-06-08 14:38
Message generated for change (Settings changed) made by nusmuk
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=507079&aid=3313799&group_id=64325

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Pixes (pix_ objects)
Group: None
>Status: Closed
>Resolution: Fixed
Priority: 5
Private: No
Submitted By: Cyrille Henry (nusmuk)
Assigned to: Nobody/Anonymous (nobody)
Summary: example 04.pix/26.framebuffer_readback crash

Initial Comment:
the example 04.pix/26.framebuffer_readback crash pd with a segfault when creating the openGL windows
this is with curent svn (rev  3971), ubuntu 10.04

I can see 2 different problem : 
- pix_snap does not create an image (pix_info after pix_snap gives only -1)
- pix_buffer_read crash when reading this image


----------------------------------------------------------------------

>Comment By: Cyrille Henry (nusmuk)
Date: 2011-06-08 20:04

Message:
yes, you are right : pix_kaleidoscope crash here.
if i remove it from the help patch, everything is now working as
expected.
(Gem revision 4025)
that was not my experience with rev 3971.

well... few hours, 54 revision latter, and this bug disappear.

thanks

----------------------------------------------------------------------

Comment By: IOhannes m zmlnig (zmoelnig)
Date: 2011-06-08 19:21

Message:
on further inspection, i can reproduce a crash if i do X-forwarding to the
amd64 machine (from a similar _32bit_ machine)

a backtrace however still points to [pix_kaleidoscope] to be the culprit.
could you run everything through gdb?

----------------------------------------------------------------------

Comment By: IOhannes m zmlnig (zmoelnig)
Date: 2011-06-08 19:21

Message:
could you provide a backtrace of the crash?

on linux/osx/similar you can use gdb for producing one:
$ gdb -args /path/to/pd -lib Gem -open /my/faulty/patch.pd
[...]
(gdb) run
[... do something to trigger the crasher bug ...]
(gdb) backtrace
[...]

----------------------------------------------------------------------

Comment By: IOhannes m zmlnig (zmoelnig)
Date: 2011-06-08 19:19

Message:
hmm, checked on an debian/sid machine with 2.6.38-2-amd64 and
nvidia-270.41.19 (and a fresh checkout of Gem) and still cannot reproduce.
i noticed that [pix_kaleidoscope] does not work _correctly_ on amd64
though, but if i turn that off, everything works as expected.


----------------------------------------------------------------------

Comment By: Cyrille Henry (nusmuk)
Date: 2011-06-08 18:44

Message:
nvidia driver
intel i7
kernel 2.6.32 / 64 bit

pix_snap does not work for framebuffer, but pix_write is working...

----------------------------------------------------------------------

Comment By: IOhannes m zmlnig (zmoelnig)
Date: 2011-06-08 18:01

Message:
weird; i'm unable to reproduce the problem.

which drivers? which architecture?

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=507079&aid=3313799&group_id=64325



More information about the GEM-dev mailing list