Received: (at submit) by bugs.debian.org; 13 Aug 1999 03:47:33 +0000 Received: (qmail 8266 invoked from network); 13 Aug 1999 03:47:33 -0000 Received: from nic.netdirect.ca (uucp@207.139.194.130) by master.debian.org with SMTP; 13 Aug 1999 03:47:33 -0000 Received: (from uucp@localhost) by nic.NetDirect.CA (8.9.3/8.9.3) with UUCP id XAA23028 for submit@bugs.debian.org; Thu, 12 Aug 1999 23:47:31 -0400 Received: (from cdfrey@localhost) by polygon.foursquare.net (8.8.6/8.8.6) id XAA10757 for submit@bugs.debian.org; Thu, 12 Aug 1999 23:46:41 -0400 Date: Thu, 12 Aug 1999 23:46:41 -0400 From: Chris Frey To: submit@bugs.debian.org Subject: svgalibg1 segfaults on mouse init Message-ID: <19990812234640.A10727@foursquare.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.6i Package: svgalibg1 Version: 1.3.1-2 Hi, I'm running potato and have svgalibg1 and svgalibg1-dev installed. When I run an svga program, say for example sabre, it segfaults on the mouse initialization, which has an fprintf in it. I believe this problem is an incompatibility with the new libc libraries and gcc 2.95. A recompile fixed it, although gcc 2.95 had trouble with the invalid __asm__ statements in svgalib. (Sorry, I have no patch for the __asm__ stuff, I used the C equivalents in my compile.) Here is the backtrace info for the core dump I got: [cdfrey: ~/games/sabre-0.2.4] gdb src/sabre core GNU gdb 4.18 [snip] #0 0x401eb188 in main_arena () from /lib/libc.so.6 (gdb) bt #0 0x401eb188 in main_arena () from /lib/libc.so.6 #1 0x2b in ?? () #2 0x40150a8c in vfprintf () from /lib/libc.so.6 #3 0x401581a1 in fprintf () from /lib/libc.so.6 #4 0x400382ae in mouse_init_return_fd () from /usr/lib/libvga.so.1 Cannot access memory at address 0x96. (gdb) - Chris -- ------------------------------------------- "Chase the dream, not the competition." - motto of the Nemesis Air Racing Team