I'm trying to create a program to test Opensplice DDS. However I'm facing some problems for which I've been stuck for quite a long time.
When I try to create a DomainParticipantFactory I got an error which says CORBA:NO_IMPLEMENT. The program works if I don't create the DomainParticipant so I thought that the problem lays there.
DDS::DomainParticipantFactory_var dpf = DDS:DomainParticipantFactory::get_instance();
// get_instance() causes the crash.
Would somebody ever faced such a problem ?
Since I've found my solution, I post here in case anyone gets it.
The problem was a misbehavior due to overlapping librairies.
I was linkings CCPP and SACPP together. That made some kind of explosive mix that the system didn't like much.
So don't link the wrong library. Depending if you use CORBA system or not, choose carefully.
Related
I coded an application using WxWidgets. When I run it. I have this error message :
assert failure failed in mswgetstyle(): unkonwn border style.
When i chose to cancel the application work fine. What does this mean.
This means that you used an invalid style somewhere in your code, it's impossible to say anything more without seeing your code.
I agree with ravenspoint comment however: your first problem is to make debugging work. You're making your life much more difficult completely unnecessarily if you can't use it.
Question Intro
I'm running an opencv project in Visual Studios 2010 and have implemented cuda support (refer to my previous question for precise info on my set-up). All cuda-functionalities are working fine - to the best of my knowledge - and are indeed improving speed on the image processing.
However, I now also wanted to attemp to speed up the video-writing function in this project by replacing the current cv::VideoWriter with the gpu::VideoWriter_GPU function. The reason for this is that the cv::VideoWriter seems to somehow cause processes running outside of the scope in which the VideoWriter is called to be slowed down, resulting in images available at the DirectShow driver being dropped by the VideoCapture-function, hence messing up an algorithm I've implemented.
Problem
To attempt to solve this issue, I've now replaced the VideoWriter-calls with VideoWriter_GPU-functionality (and corresponding syntax), but when I run my project (Compile & Run in Debug-mode), I get the following error-message (directly originating atthe calling of gpu::VideoWriter_GPU):
OpenCv Error: The function/feature is not implemented (The called functionality
is disabled for current build or platform) in unknown function, file
c:slave\builds\wininstallermegapack\opencv\modules\gpu\src\precomp.hpp, line 131.
and the program then ends with
code -529697949 (0xe06d7363)
I've purposely currently not included any of my code because the error-message originates so clearly from the call to the gpu::VideoWriter_GPU, which is making me think it's not a coding or syntax problem. (Please comment if you feel my code is necessary for answering this question.
My steps so far
I miss the natural gift of understanding what precisely this message means or how to interpret it. Does my opencv v2.4.4 simply not support what I want...? Does this function simply not work on my windows 7, 64bit system...?
I've checked out as many available google-hits I could find (relating to this error message and combinations of searchterms like "opencv, gpu, VideoWriter_GPU, disabled for current build") but have not understood what the problem is or how to solve it.
Corresponding header-file and error message can also be found here.
This post and this post suggest the error message is trying to tell me that opencv simply does not provide the option of using the function or functionality I am aiming to use. Or maybe even that cuda is not at all supported.. But that's all against my experience as every single opencv gpu-function I've tried to use has seemed to work fine.
Question
Could someone please explain to me why this is not working for me, and more importantly share with me what I should do to make the VideoWriter_GPU work?
Many thanks!
Maybe this link can give you a little idea of what the problem is: VideoReader_GPU not available, but built with NVCUVID?.
It seems to be that the problem is the CUDA_DISABLER var.
My program is exitting with code '62097' (or in hex 0xF291).
I know which DLL library is causing it, and I'm trying to figure out why it is messing up.
What does 62097 mean? How can I find out? I checked online, and as far as I can tell, generic Windows error codes don't go up to 62097.
Any other suggestions how I can go about debugging this problem?
I use Dependency Walker on the DLL that's causing trouble, but everything is fine except missing IESHIMS.dll, IEFRAME.dll, and SHLWAPI.dll (which usually are missing when I use Dependency Walker).
The library in question is a 3rd party library that I compiled myself - it's quite possible I compiled it incorrectly - how can I tell if that's the case?
The program refuses to run before it enters main(), but only if I use a class imported from the DLL. If I'm not using anything from the DLL, the program starts fine.
The program is technically "running", but in the background, before the code ever reaches me. It's not a constructor of a class, because I tried doing something like this:
dllClass *class = new dllClass;
And the same thing occurred before execution reached the 'new', so it can't be a constructor with an infinite loop or something like that.
It's running as a process, and is not "Not responding".
I'm using MinGW on Windows 7 32bit. What can I do to troubleshoot this?
I appreciate any insight you can offer; meanwhile I'm trying to follow up a few more possible thoughts hoping I can narrow it down further.
This library is made using Qt ? Because according to http://lists.qt-project.org/pipermail/development/2013-March/010157.html it the return code Qt uses when it kills a process.
I am debugging an Iphone program with the simulator in xCode and I have one last issue to resolve but I need help resolving it for the following reason: when it happens the program goes into debugging mode but no errors appear (no BAD ACCESS appears) and it does not show where the code fails. Putting some variables as global helps me to see their values to start pin pointing where the bug is but before I go into this fully I would like to know what techniques/tools you guys use to debug these situations.
If it helps Im debugging the following: I merged some code into the SpeakHere demo. The code was added in the C++ modules of the program (AQRecorder.h and .mm). I seem to have pinpointed the problem code in a function I wrote.
My favourite is always to add debugging code and log it to a file. This allows me so report any and all information I need to resolve the issue if the debugger is not working properly.
I normally control the debugging code by use of a flag which I can manipulate at run time or by the command line.
If the error is (and it probably is) a memory management issue, printing log entries is really not going to help.
I would reccomend learning how to use Instruments, and use its tools to track down the memory leak when it occurs rather than waiting until the application crashes later on.
Is there any way to use the signals without MOC and without the connecting via names? My one problem with Qt is that you have something like
this->connect(this->SaveBtn, SIGNAL(click()), SLOT(SaveClicked()));
And there is no error detection to tell that is wrong other then finding out the button doesn't work or searching through their documentation to find out the signal doesn't exist. Also it seems pointless and a waste of cycles to connect via names instead of classes.
There is error detection, the connect function returns false when it fails to connect, and a warning is output on standard error (or, on Windows, to the weird place which DebugView reads from). Also you can make these warnings into fatal errors by setting QT_FATAL_WARNINGS=1 in your environment.
It's not pointless to connect by name. For example, it means that connections can be established where the signal/slot names are generated at runtime.
Other than the fact that signals are just methods, no I don't think you can use them like they are intended without the intermediate MOC step. It is a pain when you mess up the connection and there is no flag raised. What does your last sentence mean? Can you elaborate what your problem is? Signals/Slots is not a perfect system, I don't think a perfect system exits, but it is pretty intuitive and has worked well for me.
No, there is no real way around that.
You'll have to use MOC and connect via names. But with time you'll find out that it "grows on you" and won't really bother you. Train yourself to add code in small snippets each time, testing that what you added works, and you'll have no trouble with this.
I normally Practice following style of coding,
m_pCancelPushButton = new QPushButton(tr("Cancel"));
m_pCancelPushButton->setObjectName("CancelButton");
//MetaObject Connections
QMetaObject::connectSlotsByName (this);
This enable me to write code
void Class_name::on_CancelButton_clicked()
{
//Do your job here.
reject();
}
I hope it will help you.
Thanks,
Rahul