Closed GoogleCodeExporter closed 8 years ago
Hmm... the only cross-platform crashing I'm aware of was with the debuger
(known
SDL thread issue). Care to be more specific? svn revision? GUI (gtk or Qt4)?
Since
your on OSX, X11 or native?
Original comment by sknau...@wesleyan.edu
on 12 Sep 2008 at 6:52
[deleted comment]
[deleted comment]
Backtrace, disassembly listing, and register info:
Program received signal EXC_BAD_ACCESS, Could not access memory.
Reason: KERN_INVALID_ADDRESS at address: 0x1cd6329b
[Switching to process 22962 thread 0x53c3]
dyna_start (code=0x9c4ac <dyna_start+44>) at r4300/x86/rjump.c:116
116 dynarec_stack_initialized = 0;
(gdb) bt
#0 dyna_start (code=0x9c4ac <dyna_start+44>) at r4300/x86/rjump.c:116
#1 0x0009c4b6 in dyna_start (code=0x9c4ac <dyna_start+44>) at
r4300/x86/rjump.c:91
Previous frame inner to this frame (gdb could not unwind past this frame)
(gdb) info registers
eax 0xb01c8e8c -1340305780
ecx 0x1b32c0b0 456310960
edx 0x9c4ac 640172
ebx 0x5af4c 372556
esp 0xb01c8eac 0xb01c8eac
ebp 0x26496f0 0x26496f0
esi 0x15cf32c 22868780
edi 0x110 272
eip 0x9c4d4 0x9c4d4 <dyna_start+84>
eflags 0x10286 66182
cs 0x17 23
ss 0x1f 31
ds 0x1f 31
es 0x1f 31
fs 0x1f 31
gs 0x37 55
(gdb) disassemble
Dump of assembler code for function dyna_start:
0x0009c480 <dyna_start+0>: call 0xa1646 <__i686.get_pc_thunk.cx>
0x0009c485 <dyna_start+5>: mov 0x4(%esp),%edx
0x0009c489 <dyna_start+9>: mov %ebp,0x3cbdcc
0x0009c48f <dyna_start+15>: mov %esp,0x3cbdc8
0x0009c495 <dyna_start+21>: mov %ebx,0x3cbdd0
0x0009c49b <dyna_start+27>: mov %esi,0x3cbdd4
0x0009c4a1 <dyna_start+33>: mov %edi,0x3cbdd8
0x0009c4a7 <dyna_start+39>: call 0x9c4ae <dyna_start+46>
0x0009c4ac <dyna_start+44>: jmp 0x9c4b6 <dyna_start+54>
0x0009c4ae <dyna_start+46>: pop %eax
0x0009c4af <dyna_start+47>: mov %eax,0x3cbdc4
0x0009c4b4 <dyna_start+52>: call *%edx
0x0009c4b6 <dyna_start+54>: mov 0x3cbdcc,%ebp
0x0009c4bc <dyna_start+60>: mov 0x3cbdc8,%esp
0x0009c4c2 <dyna_start+66>: mov 0x3cbdd0,%ebx
0x0009c4c8 <dyna_start+72>: mov 0x3cbdd4,%esi
0x0009c4ce <dyna_start+78>: mov 0x3cbdd8,%edi
0x0009c4d4 <dyna_start+84>: mov 0x1a371eb(%ecx),%eax
0x0009c4da <dyna_start+90>: xor %edx,%edx
0x0009c4dc <dyna_start+92>: mov %edx,0x32f943(%ecx)
0x0009c4e2 <dyna_start+98>: movl $0x0,(%eax)
0x0009c4e8 <dyna_start+104>: xor %eax,%eax
0x0009c4ea <dyna_start+106>: mov %eax,0x32f953(%ecx)
0x0009c4f0 <dyna_start+112>: xor %eax,%eax
0x0009c4f2 <dyna_start+114>: mov %eax,0x32f94f(%ecx)
0x0009c4f8 <dyna_start+120>: xor %eax,%eax
0x0009c4fa <dyna_start+122>: mov %eax,0x32f94b(%ecx)
0x0009c500 <dyna_start+128>: xor %eax,%eax
0x0009c502 <dyna_start+130>: mov %eax,0x32f947(%ecx)
0x0009c508 <dyna_start+136>: xor %eax,%eax
0x0009c50a <dyna_start+138>: mov %eax,0x32f93f(%ecx)
0x0009c510 <dyna_start+144>: ret
End of assembler dump.
(gdb)
--
roger6106
Original comment by preotgee...@gmail.com
on 22 Sep 2008 at 7:10
Fixed in build r1072. This can be closed now.
--roger6106
Original comment by preotgee...@gmail.com
on 23 Sep 2008 at 3:23
Original comment by sknau...@wesleyan.edu
on 23 Sep 2008 at 6:33
Original issue reported on code.google.com by
preotgee...@gmail.com
on 9 Sep 2008 at 3:35