sound issue on linux-ppc

June 18, 2006

Hi! Me again :rolleyes:

Just played some minutes without sound.

Everything seems to work fine so far.

Only issue, which very likely isn't ppc-related is

the missing possibility to save as of lack of the GUISAVE python module...

cheers

frostwork

Avenger · June 18, 2006

Heh, it isn't missing!

Or... you have BG1?

Hmm, i'll write it in a minute!

Avenger · June 18, 2006

Program received signal SIGSEGV, Segmentation fault.

[switching to Thread 814879968 (LWP 16764)]

ACMImp::PlayListManager () at ACMImp.cpp:159

159 MusicReader->read_samples( ( short* ) static_memory, ACM_BUFFERSIZE >> 1 );

(gdb) where

#0 ACMImp::PlayListManager () at ACMImp.cpp:159

#1 0x0f1b72ec in ACMImp::PlayListManager () at ACMImp.cpp:157

#2 0x0f1b72ec in ACMImp::PlayListManager () at ACMImp.cpp:157

#3 0x0f1b72ec in ACMImp::PlayListManager () at ACMImp.cpp:157

#4 0x0f1b72ec in ACMImp::PlayListManager () at ACMImp.cpp:157

Previous frame inner to this frame (corrupt stack?)

(gdb)

cheers

frostwork

<{POST_SNAPBACK}>

Try to catch this with valgrind!

It is almost surely a 64 bits vs. 32 bits problem.

The ACM decoder was originally written for 32 bits.

[edit]

either the acm reader, or openal itself is super buggy :rolleyes:

June 18, 2006

Hi again!

> Try to catch this with valgrind!

I would but it still exits on creating the Main Surface:

--------

[sDLVideo]: Creating Main Surface...[OK]

disInstr(ppc): unhandled instruction: 0x7E2902AC

primary 31(0x1F), secondary 684(0x2AC)

==23276== valgrind: Unrecognised instruction at address 0xF72BE5C.

==23276== Your program just tried to execute an instruction that Valgrind

==23276== did not recognise. There are two possible reasons for this.

==23276== 1. Your program has a bug and erroneously jumped to a non-code

==23276== location. If you are running Memcheck and you just saw a

==23276== warning about a bad jump, it's probably your program's fault.

==23276== 2. The instruction is legitimate but Valgrind doesn't handle it,

==23276== i.e. it's Valgrind's fault. If you think this is the case or

==23276== you are not sure, please let us know and we'll try to fix it.

==23276== Either way, Valgrind will now raise a SIGILL signal which will

==23276== probably kill your program.

==23276==

==23276== Process terminating with default action of signal 4 (SIGILL)

==23276== Illegal opcode at address 0xF72BE5C

==23276== at 0xF72BE5C: ConvertAltivec32to32_prefetch (in /usr/lib/libSDL-1.2.so.0.7.3)

==23276== by 0xF710FAC: SDL_SoftBlit (in /usr/lib/libSDL-1.2.so.0.7.3)

==23276== by 0xF741BEC: SDL_LowerBlit (in /usr/lib/libSDL-1.2.so.0.7.3)

==23276== by 0xF7432B0: SDL_ConvertSurface (in /usr/lib/libSDL-1.2.so.0.7.3)

==23276== by 0xF745D30: SDL_DisplayFormat (in /usr/lib/libSDL-1.2.so.0.7.3)

==23276== by 0xF7C22C4: SDLVideoDriver::CreateDisplay(int, int, int, bool) (SDLVideoDriver.cpp:122)

==23276== by 0xFF338DC: Interface::Main() (Interface.cpp:625)

==23276== by 0x10001974: main (GemRB.cpp:53)

[sDLVideo]: Creating Back Buffer...==23276==

----------

Now with an extra "Altivec" error... maybe I really should fall back to an older sdl... (Grrrrr)

>It is almost surely a 64 bits vs. 32 bits problem.

>The ACM decoder was originally written for 32 bits.

Maybe I missunderstand you, but the Pegasos is a 32-bits machine

> either the acm reader, or openal itself is super buggy

Mmmmh, which of both would be better? :rolleyes:

friendly,

Marcel

Avenger · June 18, 2006

oops, sorry, i thought it is a 64 bit + big endian machine :rolleyes:

Btw, i've uploaded the bg1 savegame script + an SDL video fix. It was a memory corruption problem, but i don't think it will fix the bug we hunt.

[edit]

I think you should not revert back to the old sdl. At least, it doesn't really count.

It seems to me, that valgrind doesn't recognise that machine code.

At least both versions bug out with the SAME machine code, this seems more and more like a legitimate machine code unknown by valgrind.

So, maybe really post a valgrind bug message, or try to look for a valgrind update.

June 19, 2006

Hi Avenger!

>Btw, i've uploaded the bg1 savegame script + an SDL video fix. It was a memory corruption problem, >but i >don't think it will fix the bug we hunt.

Just built up the new cvs:

The strange valgrind error still exists & unfortunately gemrb segfaults when trying to save:

----------

[KEYImporter]: Searching for GUISAVE.chu...[FOUND]

[KEYImporter]: Searching for guisrsvb.mos...[FOUND]