"G. Low" wrote: > > Hi! I've been compiling xmame for Solaris UltraSparc with no problems, until xmame > 0.69.1 came about...! > Last version I tried that compiled...ok...0.67.2...didn't try 0.68.1 though... > I'm not a developer, so I'm not sure where to start? =( > Thanks!
Do you mean the compile dumps core or the excecution? odd... I think (actually hope) this might be related: xmame 0.68.1 and 0.69.1 now generate a "bus error" when running xmame or xmess. For the last couple of days, i've been pulling my hair as to what has happened, because the xmame/xmess-0.67.1 ran fine, provided i patched here and there a bit. The patch to xmame-0.68.1 is 3 meg bz2 compressed, so i'm kinda overwhelmed what/where to look for exactly. Let me give some detailed info: SGI Origin 200 4 R12K CPU's IRIX 6.5.19 xmame-0.69.1 MIPSPro 7.3.1.3 Compiled without XV, with MITSHM, CFLAGS = -n32 -mips4 -g, IL = '-DINLINE=static __inline' (tried 'static' as well, no difference) mech003 /usr2/local/everdij/xmame/xmame-0.69.1> file xmess.x11 xmess.x11: ELF N32 MSB mips-4 dynamic executable (not stripped) MIPS - version 1 mech003 /usr2/local/everdij/xmame/xmame-0.69.1> dbx xmess.x11 dbx version 7.3.1 68542_Oct26 MR Oct 26 2000 17:50:34 run Overlapping regions: finding functions/setting breakpoints may not work reliably till program is run (rld moves DSOs, removing overlaps). Use 'stop at 1' and 'run' commands first to remove overlaps. Overlapping regions: 0xf400000 to 0xf523000 and 0xf400000 to 0xf423000 Executable /usr2/local/everdij/xmame/xmame-0.69.1/xmess.x11 (dbx) Process 190732 (xmess.x11) started Process 190732: region 5 identical to prev ignored Process 190732: region 7 identical to prev ignored Process 190732: region 9 identical to prev ignored Process 190732: region 11 identical to prev ignored Process 190732: region 13 identical to prev ignored Process 190732: region 13 identical to prev ignored warning: no mixer plugins available Process 190732 (xmess.x11) stopped on signal SIGBUS: Bus error (default) at [rc_set_option3:593 +0xc,0x110e1224] 593 *(int *)option->dest = x; And now i'm struggling from there. The "offending" routine is actually in src/unix/sysdep/rc.c but 1) it is identical to xmame-0.67.2 and 2) Bus errors occur whenever there are memory map collisions, sorta, so this can be triggered by an early malloc/setmem somewhere. Good luck finding that one :( Any hints appreciated... Frank -- drs Frank Everdij Email:[EMAIL PROTECTED] Tel:01527-88202 Room:6.08 System Administrator for Structural Mechanics Dept. of Civil Engineering TU Delft _______________________________________________ Xmame mailing list [EMAIL PROTECTED] http://toybox.twisted.org.uk/mailman/listinfo/xmame
