I did not realize I had another msgs from OS, that ocurred before the ones I show you before (thread panicked)
Is related to some stack check that fails. The first 2 second are played fine. when the error occurs first the OS send this msgs: 0:05:55.270482 sti: MCU_ASCII_PRINTF; channel:0xE0; msg:******************Crash Dispatch******************************* 00:05:55.270497 sti: MCU_ASCII_PRINTF; channel:0xE0; msg:Exc id 12 00:05:55.270521 sti: MCU_ASCII_PRINTF; channel:0xE0; msg:Exc code 500bd2e0 00:05:55.270546 sti: MCU_ASCII_PRINTF; channel:0xE0; msg:Exc data 8a600fe4 00:05:55.270563 sti: MCU_ASCII_PRINTF; channel:0xE0; msg:Exc extra 5 00:05:55.270587 sti: MCU_ASCII_PRINTF; channel:0xE0; msg:Stack 2703DE4 00:05:55.270608 sti: MCU_ASCII_PRINTF; channel:0xE0; msg:Link 500B8CBC 00:05:55.270623 sti: MCU_ASCII_PRINTF; channel:0xE0; msg:Action 0 00:05:55.270663 sti: MCU_ASCII_PRINTF; channel:0xE0; msg:Stack Test 11988DE4 00:05:55.270736 sti: MCU_ASCII_PRINTF; channel:0xE0; msg:*******User stack check (Dispatch)********** 00:05:55.270798 sti: MCU_ASCII_PRINTF; channel:0xE0; msg:*******User stack ok ********** 11988DE4 00:05:55.270826 sti: MCU_ASCII_PRINTF; channel:0xE0; msg:* 02703DE4 8A601004 00:05:55.270860 sti: MCU_ASCII_PRINTF; channel:0xE0; msg:* 02703DE8 02703E1C 00:05:55.270895 sti: MCU_ASCII_PRINTF; channel:0xE0; msg:* 02703DEC 500AF0C8 . . . . . More below is another user stack that fails 00:05:55.275370 sti: MCU_ASCII_PRINTF; channel:0xE0; msg:* 02703FF8 00000000 00:05:55.275405 sti: MCU_ASCII_PRINTF; channel:0xE0; msg:* 02703FFC 50014D44 00:05:55.275466 sti: MCU_ASCII_PRINTF; channel:0xE0; msg:*******User stack failed ********** 00:05:55.275504 sti: MCU_ASCII_PRINTF; channel:0xE0; msg:*******Kernel stack******** 00:05:55.275531 sti: MCU_ASCII_PRINTF; channel:0xE0; msg:* 80009340 00000000 00:05:55.275560 sti: MCU_ASCII_PRINTF; channel:0xE0; msg:* 80009344 1000000B . . . . .. 00:05:55.282043 sti: MCU_ASCII_PRINTF; channel:0xE0; msg:******************Crash 2******************************* 00:05:55.282133 sti: MCU_ASCII_PRINTF; channel:0xE0; msg:Thread panic KERN-EXEC 3 00:05:55.282245 sti: MCU_ASCII_PRINTF; channel:0xE0; msg:Panicked thread: Helix::HelixAudioServer (id 189) -----Original Message----- From: Eric Hyche [mailto:[EMAIL PROTECTED] Sent: Wednesday, September 21, 2005 1:17 PM To: 'Edgar Luevano'; 'Jon Recker' Cc: [EMAIL PROTECTED] Subject: RE: FW: [Audio-dev] crash when playing AAC OnDryNotification's get called when audio services does not have enough data to write to the audio device. There may still be data in the audio device and the renderer may still have data to write as well. For MIN_HEAP builds, I believe we ONLY decode when we get a OnDryNotification. Eric > -----Original Message----- > From: Edgar Luevano [mailto:[EMAIL PROTECTED] > Sent: Wednesday, September 21, 2005 1:43 PM > To: [EMAIL PROTECTED]; 'Jon Recker' > Cc: [EMAIL PROTECTED] > Subject: RE: FW: [Audio-dev] crash when playing AAC > > Thank you Eric and Jon, > I played the file locally, I will look to the audio services. > Just a little question, > dry notifications occurs when trying to write audio data, > but the buffer is empty? > Thank you > Edgar > > -----Original Message----- > From: Eric Hyche [mailto:[EMAIL PROTECTED] > Sent: Wednesday, September 21, 2005 12:25 PM > To: 'Jon Recker' > Cc: 'Edgar Luevano'; [EMAIL PROTECTED] > Subject: RE: FW: [Audio-dev] crash when playing AAC > > > > Thanks, Jon. It must be some difference in the > Symbian audio services versus the Win32 audio > services that is causing the difference. > > Edgar: you might try logging audio services writes and > dry notifications. By the way, was this local > playback or streamed? If it's streamed, then you > need to check things like loss, etc. > > Eric > > > -----Original Message----- > > From: Jon Recker [mailto:[EMAIL PROTECTED] > > Sent: Wednesday, September 21, 2005 12:51 PM > > To: [EMAIL PROTECTED] > > Subject: Re: FW: [Audio-dev] crash when playing AAC > > > > I tried playing this in PC RealPlayer with the fixed-point > > raac.dll, and it plays fine the whole way through. I also > > converted the .3gp file to ADTS format and decoded with the > > (fixed-point) Windows cmd-line decoder, ARM-ADS cmd-line > > decoder, and the ARM-Linux cmd-line decoder. It decodes > > correctly with all those as well. > > > > Nothing immediately jumps to mind why the codec would work > > okay in the PC player and Windows/Linux/ADS test harnesses, > > but not on the Symbian player. > > > > I just played this back locally. Is he streaming it? (there > > was this diagnostic message) > > > > >*********** Crash 2 *********** > > >Panicked Thread : Helix:HelixAudioServer (id 173) > > > > In addition to the codec, are there other differences between > > the PC and Symbian players that might be relevant (streaming > > code, 3GPP renderer, etc.)? > > > > - Jon > > > > At 08:38 AM 9/21/05, you wrote: > > > > >Jon, > > > > > >Edgar Luevano is reporting that the attached > > >AAC .3gp file is causing problems on Symbian. > > >Since it plays fine on RealPlayer, that led > > >me to suspect perhaps a problem with the fixed-point > > >decoder? I was going to run it through the fixed-point > > >decoder harness, but since it's in .3gp format I > > >can't do that. I guess I could forcibly replace the > > >raac.dll in RealPlayer with the fixed-point one > > >and try that. While I'm doing that, do you have > > >any other ideas? > > > > > >Eric > > > > _______________________________________________ Audio-dev mailing list [email protected] http://lists.helixcommunity.org/mailman/listinfo/audio-dev
