Login at Kodi Home

jmarshall · 2008-03-06, 01:01

I just want to point out that the IR remote plugged in or not may not be an issue. It simply has been reported as an issue in the past.

The key is we need to find out exactly where in the code it's causing faults to occur. A debug log helps, but I suspect we'll need more (i.e. we'll need someone able to run a debug build while connected to a debugger).

Cheers,
Jonathan

willers.nail · 2008-03-06, 15:21

If someone like me wanted to get a debug build how would I go about it. What is a debugger?

pt-1 · 2008-03-06, 16:16

pt-1 · 2008-03-06, 16:16

Wrong Picture...

willers.nail · 2008-03-06, 18:38

Thanks pt-1 for your input but Im already aware of that and I have already posted a normal debug log of the issue happening at the start of this thread. What I was meaning to ask about was what jmarshall meant in saying

Quote:A debug log helps, but I suspect we'll need more (i.e. we'll need someone able to run a debug build while connected to a debugger).

I think he means some specific debug build which can catch the bug but maybe I'm wrong?

djdafreund · 2008-03-07, 02:35

Well, i have mine on, and also since unplugged my IR plug, which i rarely use anyway, so next time it freezes, i'll post my log.

WeirdH · 2008-03-10, 22:09

This might be a whole different issue altogether, or may have been resolved as well, I don't know. But just in case it might prove useful, here's a little something I encountered a while ago.

I had this little pc app called xbmc_msn or something, which made it possible to make the Windows Live msn messenger show the song you were playing in XBMC, just like you can do with WMP. I thought that was pretty cool, so I tried it out.

This meant I had to turn on 'web server' in my Network Settings in XBMC. After a while I started seeing more and more seemingly random lockups. Since turning the web server option on and using the msn app, that was the first thing I turned off, to see if that was the problem. It was. The random lockups were completely gone after turning 'web server' off.

Maybe it's related somehow??

thermionic · 2008-03-21, 22:27

If I enable debugging, it doesn't lock up, if I turn debugging off, it locks up

I think my xbox hates me :-(

jmarshall · 2008-03-21, 23:16

Not necessarily. It could indicate a variable (such as a pointer) not being initialized to zero. In debug all variables are initialized on creation. In release they are not. Ofcourse that doesn't help much in tracking it down!

You can, however, run Release while attached to the debugger - if and when it crashes it should still give you a call stack etc.

Cheers,
Jonathan

thermionic · 2008-03-22, 05:57

Sorry, my bad description, I meant debug logging. I can follow what you meant, but I presume that would require the xdk and visual studio.

DrDDT · 2008-03-25, 18:40

Got a lockup, see here.

willers.nail · 2008-03-25, 20:39

I've reverted back to using the remote control on its own and haven't yet seen a single lock up in 2 - 3 weeks. This has to be when remote and pads are connected at the same time I think. Hey DrDDT what peripherals had you connected when this happened? I have compared your log to my first one and they both look identical when the fatal exception happens at the end of the debug logs.

See below for comparison

My log

Code:
#

19:42:01 M: 35057664   DEBUG: CApplication::OnKey: 166 pressed, action is 3

#

19:42:01 M: 35057664   ERROR: exception in CApplication::FrameMove()

#

19:42:01 M: 35057664   ERROR: exception in CApplication::FrameMove()

#

19:42:01 M: 35057664   ERROR: exception in CApplication::FrameMove()

#

19:42:01 M: 35057664   ERROR: exception in CApplication::FrameMove()

#

19:42:01 M: 35057664   ERROR: exception in CApplication::FrameMove()

#

19:42:01 M: 35057664   ERROR: exception in CApplication::FrameMove()

#

19:42:01 M: 35057664   ERROR: exception in CApplication::FrameMove()

#

19:42:01 M: 35057664   ERROR: exception in CApplication::FrameMove()

#

19:42:01 M: 35057664   ERROR: exception in CApplication::FrameMove()

#

19:42:01 M: 35057664   ERROR: exception in CApplication::FrameMove()

#

19:42:01 M: 35057664   ERROR: exception in CApplication::FrameMove()

#

19:42:01 M: 35057664   ERROR: CApplication::FrameMove(), too many exceptions

#

19:42:01 M: 35057664   FATAL: EXCEPTION_ACCESS_VIOLATION (0xc0000005)

#

                              at 0x8003f0b7

DrDDT Log

Code:
#

17:22:13 M: 41697280   DEBUG: CApplication::OnKey: 167 pressed, action is 4

#

17:22:14 M: 41697280   ERROR: exception in CApplication::FrameMove()

#

17:22:14 M: 41697280   ERROR: exception in CApplication::FrameMove()

#

17:22:14 M: 41697280   ERROR: exception in CApplication::FrameMove()

#

17:22:14 M: 41697280   ERROR: exception in CApplication::FrameMove()

#

17:22:14 M: 41697280   ERROR: exception in CApplication::FrameMove()

#

17:22:14 M: 41697280   ERROR: exception in CApplication::FrameMove()

#

17:22:14 M: 41697280   ERROR: exception in CApplication::FrameMove()

#

17:22:14 M: 41697280   ERROR: exception in CApplication::FrameMove()

#

17:22:14 M: 41697280   ERROR: exception in CApplication::FrameMove()

#

17:22:14 M: 41697280   ERROR: exception in CApplication::FrameMove()

#

17:22:14 M: 41697280   ERROR: exception in CApplication::FrameMove()

#

17:22:14 M: 41697280   ERROR: CApplication::FrameMove(), too many exceptions

#

17:22:14 M: 41697280   FATAL: EXCEPTION_ACCESS_VIOLATION (0xc0000005)

#

                              at 0x8003f0b7

I hope this will help the dev's to see where the problem is? If not can you tell us what else needs to be done to catch this annoying bug please.

DrDDT · 2008-03-25, 20:44

willers.nail Wrote:I've reverted back to using the remote control on its own and haven't yet seen a single lock up in 2 - 3 weeks. This has to be when remote and pads are connected at the same time I think. Hey DrDDT what peripherals had you connected when this happened? I have compared your log to my first one and they both look identical when the fatal exception happens at the end of the debug logs.

I do have a controller and an IR receiver connected!
The controller is a Logitech wireless controller on port #1, the IR port (Microsoft Original) is in port #2.

willers.nail · 2008-03-25, 22:39

Excellent exactly same setup as I have when I get these lockups so this may prove this bug does exist on most boxes using this sorta setup. Hoping Dev's can have a look and let us know what we can do to help get this thing.

DrDDT · 2008-03-26, 13:31

willers.nail Wrote:Excellent exactly same setup as I have when I get these lockups so this may prove this bug does exist on most boxes using this sorta setup. Hoping Dev's can have a look and let us know what we can do to help get this thing.

Do you also have a wireless gamepad connected?