The Mesa error is probably caused by the app trying to use an OpenGL extension
that's not supported (an app bug).

That shouldn't lead to a crash/lock-up though.

What kind of gfx card are you using?

I am using a Radeon Mobility(M7) 7500 on a Dell Inspiron 5100.

(In reply to comment #1)
> The Mesa error is probably caused by the app trying to use an OpenGL extension
> that's not supported (an app bug).
> That shouldn't lead to a crash/lock-up though.
> What kind of gfx card are you using?

Can you get a stack trace with gdb?

(In reply to comment #3)
> Can you get a stack trace with gdb?
> 

Is this what you need?

0000000a:0000000b: create process
'Z:\home\betolley\games\Westwood\Renegade\game.exe'/0x1106a0 @0078f4ef (0<0>)
wine: Unhandled page fault on read access to 0x01cb2000 at address 0x6040c0d9
(thread 0009), starting debugger...
Unhandled exception: page fault on read access to 0x01cb2000 in 32-bit code
(0x6040c0d9).
Register dump:
 CS:0073 SS:007b DS:007b ES:007b FS:003b GS:0033
 EIP:6040c0d9 ESP:0033ebb0 EBP:0033ed58 EFLAGS:00210246(   - 00      -RIZP1)
 EAX:01cb2000 EBX:6041fa28 ECX:00000001 EDX:00432000
 ESI:00000000 EDI:01880000
Stack dump:
0x0033ebb0:  01880120 01880000 003cd6a0 00000000
0x0033ebc0:  00000000 00000000 00000000 7dc469e0
0x0033ebd0:  6016825b 00000000 00000002 6041fa28
0x0033ebe0:  00000008 60161fb0 0033ec38 6041b58a
0x0033ebf0:  00000000 00000040 00000044 01880000
0x0033ec00:  01880120 00000000 00000000 00000000
fixme:ntdll:RtlNtStatusToDosErrorNoTeb no mapping for c0000119
Backtrace:
=>1 0x6040c0d9 pe_load_debug_info+0x6f9(pcs=0x1157d8, module=0x44ccb8)
[/home/betolley/Desktop/wine-0.9.23/wine-0.9.23/dlls/dbghelp/pe_module.c:177] in
dbghelp (0x6040c0d9)
  2 0x6040c794 pe_load_module+0x354(pcs=0x1157d8, name=0x33f048, hFile=0x0,
base=0x400000, size=0x4b7000)
[/home/betolley/Desktop/wine-0.9.23/wine-0.9.23/dlls/dbghelp/pe_module.c:377] in
dbghelp (0x6040c794)
  3 0x60404547 SymLoadModule+0x1b7(hProcess=0x2c, hFile=0x0, ImageName=0x33f048,
ModuleName=0x33f17c, BaseOfDll=0x400000, SizeOfDll=0x4b7000)
[/home/betolley/Desktop/wine-0.9.23/wine-0.9.23/dlls/dbghelp/module.c:419] in
dbghelp (0x60404547)
  4 0x603f94a2 process_invade_cb+0x92(name=0x33f17c, base=0x400000,
size=0x4b7000, user=0x2c)
[/home/betolley/Desktop/wine-0.9.23/wine-0.9.23/dlls/dbghelp/dbghelp.c:226] in
dbghelp (0x603f94a2)
  5 0x604042d2 EnumerateLoadedModules+0x142(hProcess=0x2c,
EnumLoadedModulesCallback=0x603f9410, UserContext=0x2c)
[/home/betolley/Desktop/wine-0.9.23/wine-0.9.23/dlls/dbghelp/module.c:663] in
dbghelp (0x604042d2)
  6 0x603fa112 SymInitializeW+0x402(hProcess=0x2c, UserSearchPath=0x0,
fInvadeProcess=0x1)
[/home/betolley/Desktop/wine-0.9.23/wine-0.9.23/dlls/dbghelp/dbghelp.c:324] in
dbghelp (0x603fa112)
  7 0x603fa1e3 SymInitialize+0xc3(hProcess=0x2c, UserSearchPath=0x0,
fInvadeProcess=0x1)
[/home/betolley/Desktop/wine-0.9.23/wine-0.9.23/dlls/dbghelp/dbghelp.c:356] in
dbghelp (0x603fa1e3)
  8 0x603a412e handle_debug_event+0x3ae(gdbctx=<register not in topmost frame>,
de=<register not in topmost frame>)
[/home/betolley/Desktop/wine-0.9.23/wine-0.9.23/programs/winedbg/gdbproxy.c:503]
in winedbg (0x603a412e)
  9 0x603a706b gdb_main+0x27b(argc=0x3, argv=0x110394)
[/home/betolley/Desktop/wine-0.9.23/wine-0.9.23/programs/winedbg/gdbproxy.c:2147]
in winedbg (0x603a706b)
  10 0x603b629d main+0x51d(argv=0x603ba7db)
[/home/betolley/Desktop/wine-0.9.23/wine-0.9.23/programs/winedbg/winedbg.c:521]
in winedbg (0x603b629d)
  11 0x603ba7db __wine_spec_exe_entry+0x5b(peb=0x7ffdf000)
[/home/betolley/Desktop/wine-0.9.23/wine-0.9.23/dlls/winecrt0/exe_entry.c:36] in
winedbg (0x603ba7db)
  12 0x602e62de start_process+0xee(arg=0x0)
[/home/betolley/Desktop/wine-0.9.23/wine-0.9.23/dlls/kernel32/process.c:822] in
kernel32 (0x602e62de)
  13 0x60022557 wine_switch_to_stack+0x17 in libwine.so.1 (0x60022557)
0x6040c0d9 pe_load_debug_info+0x6f9
[/home/betolley/Desktop/wine-0.9.23/wine-0.9.23/dlls/dbghelp/pe_module.c:177] in
dbghelp: cmpl      $1,0x0(%eax)
Unable to open file
'/home/betolley/Desktop/wine-0.9.23/wine-0.9.23/dlls/dbghelp/pe_module.c'
Modules:
Module  Address                 Debug info      Name (20 modules)
ELF     845000-860000   Deferred        ld-linux.so.2
ELF     862000-995000   Deferred        libc.so.6
ELF     997000-9bc000   Deferred        libm.so.6
ELF     9be000-9c2000   Deferred        libdl.so.2
ELF     af7000-b0b000   Deferred        libpthread.so.0
ELF     6001b000-6012c000       Stabs           libwine.so.1
ELF     60277000-60386000       Stabs           kernel32<elf>
  \-PE  60290000-60386000       \               kernel32
ELF     60386000-603cd000       Stabs           winedbg<elf>
  \-PE  60390000-603cd000       \               winedbg
ELF     603cd000-603e2000       Deferred        psapi<elf>
  \-PE  603d0000-603e2000       \               psapi
ELF     603e2000-60428000       Stabs           dbghelp<elf>
  \-PE  603f0000-60428000       \               dbghelp
ELF     60428000-6046e000       Deferred        advapi32<elf>
  \-PE  60430000-6046e000       \               advapi32
ELF     68b02000-68b0d000       Deferred        libnss_files.so.2
ELF     68b78000-68bf9000       Deferred        ntdll<elf>
  \-PE  68b90000-68bf9000       \               ntdll
ELF     7bf00000-7bf03000       Deferred        <wine-loader>
Threads:
process  tid      prio (all id:s are in hex)
0000000a
        0000000b    0
00000008 (D) c:\windows\system32\winedbg.exe
        00000009    0 <==

I booted into knoppix with dri 6.4.1.  the game worked great. it has to be a bug
in 6.5.1.  How can i find out what opengl call it is calling?  also if i point
to an invalid directory for the dri driver the game run in software
acceleration.  slowly.....


(
In reply to comment #3)
> Can you get a stack trace with gdb?
> 

Hi, I have the same card (Radeon 7500 M7), except on my ThinkPad T40. I get the same error when trying to launch Savage on my Ubuntu 7.04:

vadi@vadi-laptop:~/.Games/SavageFE$ ./savage.sh
System_Init()
Mesa 6.5.2 implementation error: User called no-op dispatch function (an unsupported extension function?)
Please report at bugzilla.freedesktop.org
TexCoord2f: 1
vadi@vadi-laptop:~/.Games/SavageFE$ 

I don't know how to get the stack though.

I'd say run your program with gdb, set a breakpoint in _mesa_problem(), then get a stack trace with 'where' when it stops.

But it looks like savage.sh is a shell script, not a binary, so you may have to examine the shell script to find out how the binary is run, and do that yourself, but with gdb.

Thirteen year old bug, closing.