#230 "Breakpoint reached" error when launching mplayerc

open
nobody
None
5
2007-08-14
2007-08-14
drnick
No

Over the last few days, ive been getting the following error when launching mplayerc.exe

====start error msg======
The exception Breakpoint
A breakpoint has been reached.
(0x80000003) occured in the application at location 0x0047505b.

Click OK to terminate the program
Click CANCEL to debug the program
====end error msg========

screenshot attached (also available at http://i181.photobucket.com/albums/x153/drnick0/misc/mplayerc_break.jpg\)

im running winxp sp2, on an IBM T43 Thinkpad.
As far as i know, there were no changes that happened to the system at the time this error message started appearing.

Thanks,
Nick

Discussion

  • drnick
    drnick
    2007-08-14

    mplayerc error screenshot

     
    Attachments
  • drnick
    drnick
    2007-08-14

    Logged In: YES
    user_id=1867245
    Originator: YES

    also, forgot to mention, though its probably obvious from the error... the application doesnt launch when clicking either OK or cancel... just thought id mention it for completeness :)

     
  • Logged In: YES
    user_id=412125
    Originator: NO

    The root cause of this problem is that mplayerc was built with an old version of the detours.lib from microsoft. You need to download the latest (2.1) version, and commit that into the source tree and rebuild. I am pretty confident that that will fix the problem.

    [I just spent an hour diagnosing this problem before I found that someone else had the exact same problem].

    [For the curious, the old version of the detours library cannot cope with 'short jumps' in the function header and copies them incorrectly. This is the excerpt that handles this case from detours.cpp:

    else if (pbCode[0] == 0xeb) { // jmp +imm8
    // These just started appearing with CL13.
    PBYTE pbNew = pbCode + 2 + *(CHAR *)&pbCode[1];
    DETOUR_TRACE(("%p->%p: skipped over short jump.\n", pbCode, pbNew));

     
  • camaroz
    camaroz
    2008-02-02

    Logged In: YES
    user_id=1998733
    Originator: NO

    So how do you fix this problem? I'm having the same issue.