Results 1 to 10 of 426

Thread: Runtime Error

Hybrid View

  1. #1
    Player
    Yoseph's Avatar
    Join Date
    Aug 2013
    Posts
    35
    Character
    Brother John
    World
    Balmung
    Main Class
    Arcanist Lv 38
    Found this at MS:

    Description of the R6025 run-time error in Visual C++

    Calling a pure virtual function is a programming error, so you need to find the call to the pure virtual function and rewrite the code so it is not called.

    One way to find a call to a pure virtual function is to replace the pure virtual function with an implementation that calls the Windows API function DebugBreak. When using the debugger, DebugBreak will cause a hard-coded breakpoint. When the code stops running at this breakpoint, you can view the callstack to see where the function was called.

    Another way to find a call to a pure virtual function is to set a breakpoint on the _purecall function that is found in PureVirt.c. Breaking on this function has the advantage of keeping the stack intact so that you can trace what is occurring.

    >>>>>end<<<<<<<
    this is a programming error

    SE is the only one that can fix it
    (1)

  2. #2
    Player
    KingofDunkshire's Avatar
    Join Date
    Sep 2013
    Posts
    23
    Character
    Jesse Dunkshire
    World
    Gilgamesh
    Main Class
    Marauder Lv 70
    Quote Originally Posted by Yoseph View Post
    Found this at MS:

    Description of the R6025 run-time error in Visual C++

    Calling a pure virtual function is a programming error, so you need to find the call to the pure virtual function and rewrite the code so it is not called.

    One way to find a call to a pure virtual function is to replace the pure virtual function with an implementation that calls the Windows API function DebugBreak. When using the debugger, DebugBreak will cause a hard-coded breakpoint. When the code stops running at this breakpoint, you can view the callstack to see where the function was called.

    Another way to find a call to a pure virtual function is to set a breakpoint on the _purecall function that is found in PureVirt.c. Breaking on this function has the advantage of keeping the stack intact so that you can trace what is occurring.

    >>>>>end<<<<<<<
    this is a programming error

    SE is the only one that can fix it
    What is sad is SE probably won't fix it or at least continue to believe it's something on our end since their ego is so absurd the past few years. I've been saying this since I first got it (last day of open beta) that this error is on SE end and that it's a program error on their part.
    (1)

Tags for this Thread