i made a program using Qt for Symbian, its all working very well ... However, it always exits with a status code -10737something when i close the program
i think the problem is in the deconstructer, maybe some memory leaks ... any suggestion on how to solve this problem, or to find the error using Qt Creator?
thanks
Record the exact number, convert it to hexadecimal, then put the result into a search engine and see what you can find.
The exit code you've got is most likely an error code which would normally be represented in hexadecimal (but the operating system has chosen to report program exit codes in signed decimal format).
Symbian defines a lot of globally used error codes. The most complete error code reference I know of can be found on newlc.com page.
If you post the question on SO, please be as precise as possible, don't write "I got -128903something error, please help", because the answer to the question phrased this way is "You've got an error somewhere in your code".
So if you need more help, post the error code with all details.
Related
I am new to Intel Pintools, and am trying to write a pintool that stops at a given instruction type and then looks for specific instructions following it in the section. I've got the xed decoding working, but I am stuck at the part where I get the actual hex opcode. How can I do that?
I would love to use INS_Opcode() -- but these are instructions that haven't been executed yet (and may never be), so they aren't INS objects. There's xed_operand_values_get_iclass(), but that returns an iclass enum, not the actual primary opcode. I see from the xed header files that there are some raw buffers associated with the various xed structures, but it is not at all clear to me how I can use that to get the information I need. Can anyone enlighten me?
Apparently I missed it the first time I looked at the header files, but there's xed3_operand_get_nominal_opcode(), which does exactly what I need it to. Related: grep is a wonderful thing.
I have a UBE that is failing after making a call to a jdeObjectCall. The API returns a 1, indicating a warning, which indicates to the report to stop processing.
The image below shows the jdeObjectCall in question that is returning a 1.
I'd like to determine why jdeObjectCall is returning a warning, so that I can investigate a fix.
Any help on this is greatly appreciated!
Cheers, Cam.
I was able to determine the answer to this question with some help from the forum jdelist.com. The topic in which I discovered my answer can be found here: https://www.jdelist.com/vb4/showthread.php/53758-E1920-Debugging-jdeObjectCall
The way I found my solution is as follows. Apologies for the high-level steps. There is some assumed knowledge here. If you are interested in a more in-depth explanation of one of these items please comment and I will provide it.
Enable logging in the jde.ini file.
Debug the locally.
Examine the output of the log file using a tool like JDETrace.
You can do a search for your business function within JDETrace. In my case, I searched for EditDate.
The line in the log will let you know the name of the busines function object.
Checkout the object in object management workbench.
Find the line where the EditDate function exists.
Place a breakpoint on this line and continue debugging.
I've recently been encountering this error when compiling OpenCL kernel files with my LLVM_IR pass:
aoc: ../../../TargetRegisterInfo.cpp:89: const llvm::TargetRegisterClass* llvm::TargetRegisterInfo::getMinimalPhysRegClass(unsigned int, llvm::EVT) const: Assertion `BestRC && "Couldn't find the register class"' failed.
I'm not sure what this means. What I've read from the documention doesn't make a lot of sense. Basically it means the backend doesn't know what type to place into the register?
Does anyone know what the error means?
It occurs in various kernels and doesn't seem to have a definitive pattern I can show as an example. I can post more details if needed, but really I'd just like to know what the error is telling me.
Thanks ahead of time for any help.
UPDATE:
It seems this command in LLVM is causing the issue:
AllocaInst* llvm::IRBuilder< preserveNames, T, Inserter >::CreateAlloca(Type * Ty, Value * ArraySize = 0,const Twine & Name = "")
It creates this error when I do a nonspecific allocation in this manner. The reason I use this command is that sometimes in a kernel there will be a store value that is a Constant. Since LLVM often requires a Value I needed a way of converting it. So I do a an allocation with an immediate store and load. This was suggested by another SOF user. Does anyone know an alternate method of converting a Constant to a Value in LLVM?
Thanks all.
Ok it seems a conventional:
Value *new_val = dyn_cast<Value>(old_val);
Works perfectly fine. Hopefully this knowledge will help someone else.
UPDATE3: Scratch that. Dynamic cast doesn't convert Constant to a Value type. So if anyone knows how to do that, please let me know.
I admit I don't understand the assertion error you get. However:
The reason I use this command is that sometimes in a kernel there will be a store value that is a Constant. Since LLVM often requires a Value I needed a way of converting it. So I do a an allocation with an immediate store and load.
That doesn't make sense to me:
Any llvm::Constant is already an llvm::Value
Storing a value and then loading it back seems like an expensive nop...
I'm doing development for Blackberry 10 using Cascades, which includes QT and QML. I find that I sometimes make mistakes in my QML file, but they don't get picked up at compilation time. How can I check whether I've made a syntax error, or mis-named a function call, or other typical errors?
QML is a dynamic language that is evaluated at Runtime. There is no compilation step and due to the nature of javascript and the dynamic nature of the global context there is no way for it to tell if what you are writing is correct/incorrect until it is evaluated. QtCreator can help with some of the QML errors you will find, but there is unfortunately no good way to get syntax errors about your javascript until it is evaluated and it explodes.
Personally, I have found good usage of the debugger to be the key to making these sort of fixes easy.
tldr; Keep your javascript clean and to a minimum there is no compile time checking.
open terminal in IDE connect your device or emulator using blackberry-SSH after connecting enter slog2info it show syntax and all typical error JavaScript with description and line NO.
If there are any mistakes it will show those lines in RED marks. It is dynamically checks there is no need to worry about compile.
If you done wrong you will not see the DESIGN CONSOLE correctly.
Project was doing fine, running fine, compiling fine. Until some seemingly random time it stopped being fine.
At the moment I'm getting around 200 stray errors:
./new:4: error: stray '\376' in program
./new:4: error: stray '\377' in program
./new:5: error: stray '\376' in program
./new:5: error: stray '\377' in program
From reading other posts it seems I have some bad characters in my code which I cannot see. So I emptied the whole file I was working on, but no luck. This error persists whatever I do.
Also, when compiling main.cpp (which it does first), it first and foremost includes #include , which is the start of the chain of "from 'file'" messages. This means it didn't really parsed much of main.cpp yet but gets borked from reading internal Qt files?
I'm totally gazing in the dark here, what could this possible be, and how would I resolve this?
Thank you!
I'm using Qt 4.7.2, GCC 4.5.0 and Win7.
Copy your code into notepad and save it. Then remove your main.cpp and add the notepad one to your project. Rebuild and check the result. If it still persists then most probably the problem is not with your source but with the Qt or gcc and/or gnulibc libraries. They probably got corrupted or are stored in a different, unsupported encoding.
Octal \376 \377 is 0xFEFF, which is the Unicode Byte-Order Mark. It is used to signal the endianness of a UTF-16 text file, and also to signal that a file is UTF-8-encoded. It should only occur at the start of a file, but it seems to have crept into the header comments in your library header file new, at lines 4 and 5. Locate this file, and delete those lines. (But only if they're comments!)
to me things like these happend in the past when I copied source from some web page. Only typing it again solved the issue. But maybe some tool to convert the encoding might fix the issue as well.
Your source file is probably encoded in UTF-16 or something like that.
Try copy-pasting the code in a new file and see if that helps.
A conflict might exist. For example, I created a project named QTcpServer.pro, but when I tried to #include QTcpServer, I got many stray errors. Renaming my project (QTcpSvr.pro) solved this error.