On Sun, 2004-03-07 at 23:34, Felix Kühling wrote:
> > > Found it. I had already fixed this problem yesterday, but not committed
> > > it yet, because it didn't fix the problem I was actually hunting. ;-)
> > > I've committed it now. A patch is attached for your convenience. Apply
> > > it in mesa/s
On Sun, 07 Mar 2004 22:44:45 +
Sérgio Monteiro Basto <[EMAIL PROTECTED]> wrote:
> On Sun, 2004-03-07 at 01:37, Felix Kühling wrote:
>
[snip]
> >
> > Found it. I had already fixed this problem yesterday, but not committed
> > it yet, because it didn't fix the problem I was actually hunting. ;
On Sun, 2004-03-07 at 01:37, Felix Kühling wrote:
> > > > Program received signal SIGSEGV, Segmentation fault.
> > > > 0x40757507 in generic_interp (ctx=0x0, t=0.918080449, edst=96,
> > > > eout=21, ein=22, force_boundary=0 '\0')
> > > > at t_vertex.c:736
> > > > 736 a[0].insert[4
On Sun, 7 Mar 2004 02:12:54 +0100
Felix Kühling <[EMAIL PROTECTED]> wrote:
> On Sat, 06 Mar 2004 20:16:38 +0100
> Michel Dänzer <[EMAIL PROTECTED]> wrote:
>
> > On Sat, 2004-03-06 at 17:08, Sérgio Monteiro Basto wrote:
> [snip]
> >
> > [...]
> >
> > > Program received signal SIGSEGV, Segmentati
On Sat, 06 Mar 2004 20:16:38 +0100
Michel Dänzer <[EMAIL PROTECTED]> wrote:
> On Sat, 2004-03-06 at 17:08, Sérgio Monteiro Basto wrote:
[snip]
>
> [...]
>
> > Program received signal SIGSEGV, Segmentation fault.
> > 0x40757507 in generic_interp (ctx=0x0, t=0.918080449, edst=96,
> > eout=21, ein=
On Sat, 2004-03-06 at 17:08, SÃrgio Monteiro Basto wrote:
> On Sat, 2004-03-06 at 15:21, Michel DÃnzer wrote:
> > On Sat, 2004-03-06 at 15:21, SÃrgio Monteiro Basto wrote:
> >
> > > Program received signal SIGFPE, Arithmetic exception.
> > > [Switching to Thread 16384 (LWP 28125)]
> > > 0x4075d064
On Sat, 2004-03-06 at 15:21, Michel Dänzer wrote:
> On Sat, 2004-03-06 at 15:21, Sérgio Monteiro Basto wrote:
> > On Sat, 2004-03-06 at 11:46, Michel Dänzer wrote:
> > > You need to get a stack trace with gdb or at least catchsegv.
> > Is this a stack trace ?
>
> [...]
>
> > Program received sign
On Sat, 2004-03-06 at 15:21, SÃrgio Monteiro Basto wrote:
> On Sat, 2004-03-06 at 11:46, Michel DÃnzer wrote:
> > You need to get a stack trace with gdb or at least catchsegv.
> Is this a stack trace ?
[...]
> Program received signal SIGFPE, Arithmetic exception.
> [Switching to Thread 16384 (LWP
On Sat, 2004-03-06 at 11:46, Michel Dänzer wrote:
> You need to get a stack trace with gdb or at least catchsegv.
Is this a stack trace ?
if I can do anything more? it will be a honor
thanks
--
Sérgio M. B.
#gdb foobillard
GNU gdb Red Hat Linux (5.3.90-0.20030710.41rh)
Copyright 2003 Free Sof
On Sat, 2004-03-06 at 04:31, SÃrgio Monteiro Basto wrote:
>
> On FooBillard-2.9 gives me a segment fault but at least doesn't hang my
> laptop.
No problems with foobillard here.
> configure foobillard-2.9 with --enable-debug:
>
> here is the results:
You need to get a stack trace with gdb or
On Thu, 2004-03-04 at 18:07, Michel Dänzer wrote:
>
> So does BillardGL here now, thanks!
yes, FooBillard-2.8 works without warnings and now I have correct fonts
in menus (when we press Esc)
On FooBillard-2.9 gives me a segment fault but at least doesn't hang my
laptop.
configure foobillard-2.9
On Thu, 2004-03-04 at 18:18, Brian Paul wrote:
>
> I think I've found the problem. I think the problem occurs when
> BillardGL compiles a glBlendFunc() call into a display list.
>
> When Ian did the BlendFunc -> BlendFuncSeparate changes he yanked the
> code that setup a dispatch table entry f
12 matches
Mail list logo
