I was wondering whether there has been any update on this particular
bug... It seems that the problem has not been solved by any recent
port update, because I am still getting the same error to this day on
an up-to-date system. Any light at the end of the tunnel :-) ?
thanks again for your attention and support
On Wed, Apr 14, 2010 at 3:23 PM, Garrett Cooper <yanef...@gmail.com> wrote:
> On Wed, Apr 14, 2010 at 5:09 AM, Dmitry Marakasov <amd...@amdmi3.ru> wrote:
>> * Giuseppe Pagnoni (gpagn...@gmail.com) wrote:
>>> First of all, let me apologize for the re- and cross-posting , but after a
>>> couple of weeks scouring the web and forums to no avail, I thought I would
>>> try again and query the FreeBSD mother source...
>>> I installed pyglet from the ports (latest version as of yesterday,
>>> py26-pyglet-1.1.2_1) on a FreeBSD 8.0 amd64 box, running the latest version
>>> of the ports' nvidia driver (nvidia-driver-195.36.15). I found that I
>>> cannot use either font.Text or text.label without causing segfaults. Here
>>> is some sample code that makes python crash:
>> The problem is most likely 64 bits. On FreeBSD 8/i386/nVidia I don't
>> see any crashes. You should try rebuilding pyglet and python
>> WITH_DEBUG and run your testcases under gdb.
> We need make.conf information for reproduction purposes.
Dip. Scienze Biomediche
Univ. di Modena e Reggio Emilia
Via Campi 287
I-41125 Modena, Italy
firstname.lastname@example.org mailing list
To unsubscribe, send any mail to "freebsd-amd64-unsubscr...@freebsd.org"