Subject:
|
Re: ldglite 0.9.4
|
Newsgroups:
|
lugnet.cad.dev
|
Date:
|
Thu, 6 Dec 2001 01:47:50 GMT
|
Viewed:
|
1199 times
|
| |
|
|
In lugnet.cad.dev, Don Heyse writes:
> In lugnet.cad.dev, Jacob Sparre Andersen writes:
> > Hmmm... I tried in Bash, and suddenly it worked.
> >
> > Tried again in Tcsh, and it didn't work. Ran `limit
> > stacksize unlimited` and tried again. Then it worked.
> > Apparently you allocate some data on the stack without
> > checking if the allocation succeeds or not.
>
> I guess I'll have to login sometime tonight and try to
> debug it from tcsh to see what's going on.
It looks like the OSMesa driver doesn't like it when you
call glutGet(GLUT_SCREEN_WIDTH). I would have thought that
was a reasonable way to get the maximimum bitmap dimensions,
but I guess the Mesa folks decided a new extension was needed
instead. Oh well.
For now the workaround is to go with a maximum stack size,
or pass an image size on the commandline to ldglite. Use
-v6 to get a 1280x1024 bitmap. These are the max dimensions
for OSMesa unless you specifically rebuild Mesa with larger
limits.
I'll fix the ldglite code for the next release.
have fun,
Don
|
|
Message is in Reply To:
 | | Re: ldglite 0.9.4
|
| (...) Yuck. I'm not allocating anything really HUGE on the stack. Plus I can't think of a good way to check in C if a stack allocation fails. On the other hand, the offscreen image buffer IS huge, but that's allocated on the heap, and I do check to (...) (23 years ago, 3-Dec-01, to lugnet.cad.dev)
|
13 Messages in This Thread:
  
- Entire Thread on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
|
|
|
|
