Printable View
I've been recently recieving the 6025 runtime error quite a bit. So, I decided to take a look at the error report and look through scripts and dlls.
I just found 2 dlls with different names that are essentially the same script. They both reference all the same errors. Could these dlls be causing the errors? or are they just running the command when the error happens?
Thanks and all the best
concrete Building
I don't believe you can get any clear answer to such a vague problem description. Try to add real details.
What details should I add?
Each and every possible.
I have to admit, I got nothing from this text. How did you find those dlls? How do you know they are the same? What does it mean "reference the same errors"? What the errors are? "Could they be causing errors?" Well, they might be, or might not. "Are they just running the command?" What is a command from dll perspective?Quote:
I just found 2 dlls with different names that are essentially the same script. They both reference all the same errors. Could these dlls be causing the errors? or are they just running the command when the error happens?
Sorry, you speak some language that I do not understand. :)
Ok. So I opened up the dll files (They have different names, so that's why I'm guessing that they're different) which were in the folder of the program. After all the squares and symbols, they both look like this:
SING error
DOMAIN error
R6034
An application has made an attempt to load the C runtime library incorrectly.
Please contact the application's support team for more information.
R6033
- Attempt to use MSIL code from this assembly during native code initialization
This indicates a bug in your application. It is most likely the result of calling an MSIL-compiled (/clr) function from a native constructor or from DllMain.
R6032
- not enough space for locale information
R6031
- Attempt to initialize the CRT more than once.
This indicates a bug in your application.
R6030
- CRT not initialized
R6028
- unable to initialize heap
R6027
- not enough space for lowio initialization
R6026
- not enough space for stdio initialization
R6025
- pure virtual function call
R6024
- not enough space for _onexit/atexit table
R6019
- unable to open console device
R6018
- unexpected heap error
R6017
- unexpected multithread lock error
R6016
- not enough space for thread data
This application has requested the Runtime to terminate it in an unusual way.
Please contact the application's support team for more information.
R6009
- not enough space for environment
R6008
- not enough space for arguments
R6002
- floating point support not loaded
Afterwards is more symbols and squares.
The reason why it's put an exclamation mark above my head is that they both look like this, so there's a pattern. Or that's what I'm thinking.
And when I said "command", the command is what the script tells the program to do.
Searching texts in the binary files, between "squares and symbols", is not a practical solution.
Instead, look in the errors documentation.
See, for example:
C Run-Time Errors R6002 through R6025
Description of the R6025 run-time error in Visual C++
I did look in the error report, but all it gives me is the command, it doesn't give me where it was from. Would you have an idea of where it could be from? I want to use the DebugBreak, but I don't want to put it anywhere I shouldn't.
Put breakpoint(s) then take a look on Call Stack window.Quote:
Originally Posted by concrete Building
That 'command' again. :) Those are error codes and desctiptions, not commands. And that errors data look the same just because they are the same, and originated from the library commonly used all over. It's CRT also known as C runtime library. This explains as well why you can find such fragments not so rare in executables and dlls.Quote:
Originally Posted by concrete Building
Now you know the truth... :)Quote:
Would you have an idea of where it could be from? I want to use the DebugBreak, but I don't want to put it anywhere I shouldn't.