-
Strange variable and pointer values in debugger with Insure++
In running an insure built executable under the debugger when examining things like READ_UNINIT_MEM errors that insure has reported you may notice '0xdeadbeef' Or '0xefbeadde' (depending on whether you're on a big endian or a little endian machine) in hex the registers This is part of how insure checks for things that are…
-
Receiving "Warning: unable to instrument ..." during compilation
If during compilation you get a message, similar to: Warning: unable to instrument "leakscop.c" (3), compiling original source code
Technical support is available at http://www.parasoft.com/insure_instrumentation_failure This message means that this source file will not be instrumented. The cause could be any of:* A…
-
Getting summaries from programs that don't exit
If you have a program that runs perpetually i.e client/server application daemon, service or something similar to any of these. You will typically not get a summary from insure because insure does not create the summaries until after exit has been called. There are couple of things that can be done about this 1. you can…
-
About SIGSEGV segmentation fault
seg fault when compiling with insureWhen running my program it gives a segmentation fault if it is compiled with insure, but if not compiled with insure, it doesn't. The only change between the Insure build and the non-Insure build is the word "insure" before the g++ statement. If it's a genuine seg fault scenario, can you…
-
Getting an assertion failure when instrumenting takes a large amount of memory
The application I am instrumenting allocates large amounts of memory, so much that it exceeds the default 256M heap limit imposed by AIX 5's libc, so I have to compile the application with -Wl,-bmaxdata:0x80000000. When running under insure, the program runs for a while and allocates approx 168M before it crashes with the…
-
Insra redirection to another machine
We are using insure-compiled binaries on various embedded products (real target x86 machines and simulated targets using User-Mode Linux). Insure works fine using stdout or a file as argument to insure++.reportfile. The target machines does not have any xserver, so its not possible to run insra on the target. Is it…
-
Using rpath on executable link with Insure++
use of rpath in executablesrpath on .so and executables Insure++ Version 7.0.1 (build 2004-10-30) Linux 2.4.20-8, RH9 gcc (GCC) 3.2.2 20030222 (Red Hat Linux 3.2.2-5) I am trying to build an application which uses .so and includes an rpath in the link. The flags in question are -Wl,-rpath . -Wl,-rpath ../lib . When insure…
-
Querstion on Insure++ suppression
Problem: When testing his application I get lots of errors reported from libXt.so library (one of X Window System graphical libraries, I'm on Linux). There are so many of these messages that I have hard time sifting through them to find the errors reported in my code. Question: Is there a way to suppress violations/errors…
-
What do I do about "error LNK2011"?
The short answer: turn pch off. The warning: Some projects fail to build when you turn pch off. The longer answer: One can not mix the use of instrumented and uninstrumented precompiled headers in the compilations of object files destined to become part of a single executable. If instrumented and uninstrumented precompiled…
-
My project doesn't build when I turn pch off
Sometimes a project that uses precompiled headers fails to compile or link under Insure++. For such projects, it is sometimes necessary to turn pch off when instrumenting your code with Insure++. However, some projects will only build if PCH is turned on. Such projects are broken. They are usually just poorly configured…
-
Turning off suppressed messages
I want nothing suppressed I have tried removing every reference to suppressed in all .psrc files but things are still suppressed How do I see everything? thanks josh siegel
-
Bad PCH usage detected
Pre-compiled headersWARNING: Bad PCH usage detected, .\MyFile.cpp will not be instrumented. This error is caused by the use of pre-compiled headers in a Microsoft VS build. The use of PCH interferes with Insure++'s ability to properly instrument your code so this warning message is shown. To solve it you simply need to…
-
How do I debug a COM object with Insure++?
COM objects are always run in some process. Often, you will know if a COM object is "in process" or "out of process". Either way, the COM object is in some process, and that process must be debugged with InsureSpy.exe, inject.exe, or Visual Studio through clicking on the "Insure++ Debug" button. You cannot attach to a…
-
Log does not include detailed information frome execution
hello i am new to insure++. i read through the manual and i believe i compiled my source correctly. but the log files are not showing the informations that i am looking for. following contents are from the log files: MEMORY LEAK SUMMARY =================== 53 outstanding memory references for 1260 bytes (1K). Leaks…
-
Debugging child process from inject
Debug child process from inject?Hello, I've been using the "Debug child processes" flag in insra (in File > Run dialog) to debug a console application on Windows. I would like to do something similar with inject on the command line. I looked through the docs and couldn't find any inject option to do this. Thanks in…
-
Memory/ImageList.cc:206 assertion failed
Possible Insure crashI have an application that dynamically loads shared libraries and resolves an init function table. When I run it with insure it crashes with the error "Memory/ImageList.cc:206 assetion failed". Is this an insure problem or something wrong with my application? I have stripped the application down and…
-
BOGUS_LEAK explained
unexplained errorsWhen running my application, I get a couple messages of the form "BOGUS_LEAK" and a couple references to where in the code some memory is being allocated and where Insure++ thinks it might be getting deleted (I think). The manual has no entry on the message BOGUS_LEAK. Can someone fill me in on that?
-
Application Hangs
There are times when running an executable that was built with Insure++ that it appears to "hang". Let us first characterize what "hanging" could be. i.e. Is it consuming CPU time? Is it consuming all available RAM and swapping to disk? Does it appear to be stuck in some kind of endless loop? Does it appear to be…
-
Compilation is too slow
I try to compile my CORBA c++ servers with Insure. But compilation is too slow - already 2 or 3 days. Is it possible to configure Insure to become more fast?
-
Using Insure++ with CGI programs
There are three issues to consider when using Insure++ with CGI programs: * Shared libraries * The .psrc file (and license information) * Output and banners ===Shared Libraries=== Where does the exe find shared libraries? If you are running the program on the same machine it was compiled on, there are no problems. If you…
-
Debugging an ISAPI dll
How to Debug an ISAPI dll with Insure++Other than the standard way to debug NT services (which is described in the Insure++ manual in the "Usage Options" section), IIS provides special hooks for debugging ISAPI extension dlls. Because the process is a little complex, I'm only posting links to relevant articles for now. a…
-
Instrumentation taking a long a time to execute.
I have a very large application, that normally takes about 3 minutes to perform all its memory allocations. It never seems to finish even the allocation phase with insure. I let it run all night, in the morning it was still allocating. One of my co-workers said that insure enters an infinite loop whenever it encounters a…
-
Building on One machine to run on another with the same architecture
In order to build on one machine and run on another machine of the same architecture First the concerns for all Unix based platforms The bin and lib directories have to have been created on the run machine in the same directory tree as on the build machine. So if you were running on a Solaris machine and on your build…