 | | Re: video card
|
|
(...) You could also try adding this: if ((!strcmp(verstr, "1.1 APPLE-1.1")) && (!strcmp(vendstr, "Apple")) && (!strcmp(rendstr, "Generic")) ) { printf("Stencil buffer disabled for XOR with Apple driver.\n"); // Generic Apple driver has problem with (...) (24 years ago, 26-Feb-02, to lugnet.cad.dev.mac)
|
| |
| | Re: how to get a debugger going
|
|
(...) Suggestions besides fighting with gdb: are you sure the keyboard() routine is getting to glutPostRedisplay() ? this is at the bottom of keyboard(). You could add a printf() there to find out. Maybe your 'E' key case is returning early? If it's (...) (24 years ago, 25-Feb-02, to lugnet.cad.dev.mac)
|
| |
| | Re: how to get a debugger going
|
|
(...) You could try running ldglite in the background to give gdb control of the console. Try this on the command line: ldglite blah blah blah & Then attach the debugger. Or maybe in gdb try: r blah blah blah & It might help, but I'm not positive. (...) (24 years ago, 25-Feb-02, to lugnet.cad.dev.mac)
|
| |
| | how to get a debugger going
|
|
Now that I've got some bugs, I'd like to get into the code with a debugger. In particular, I am trying to set a breakpoint in the keyboard() method so that I may trace the execution of key commands. Id like to figure out why pg-up/pg-down refreshes (...) (24 years ago, 25-Feb-02, to lugnet.cad.dev.mac)
|
| |
| | Re: video card
|
|
(...) I have tried all 4. The differences are subtle, I'm not sure I see them all. I like -le the best because I can see the entire model on each refresh. (...) I commented this out but it did not make the trailing go away. I can always get the (...) (24 years ago, 25-Feb-02, to lugnet.cad.dev.mac)
|
