Databases
StackOverflow2013
Postsdbo
POdll in debug mode, calling program in release mode (and vice versa)
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POdll in debug mode, calling program in release mode (and vice versa)
    primarykey
    data
    text
    <p>I'm writing a small C++ program that tests C dlls, containing some functions. Those dlls exist in a debug version and a release version and I would like to load them both with the same program and compare them with a previous version. </p> <p>The problem is, when I compile my program with release config, it can only use the dlls that are also release, and when I compile the program using debug config it can only use dlls that are also debug. </p> <p>I load the dlls/functions using LoadLibrary and GetProcAddress functions. </p> <p>There are two types of functions: <code>void type1(int&amp;)</code> and <code>void type2(vector&lt;string&gt;*)</code>. Type 1 works fine no matter the configuration. But type 2 only works when the configuration matches. </p> <p>Code: <code><pre> typedef void(*GetNames)(vector<code>&lt;string&gt;*</code>); GetNames get_var_names = (*GetNames)GetProcAddress(dll,"get_var_names"); vector<code>&lt;string&gt;</code> var_names; get_var_names(&amp;var_names); </pre></code></p> <p>The last line is where the program fails with an error like "0xC0000005: Access violation reading location 0xbaadf008." if the configuration of calling program and dll don't match. The error is a reading violation when program is release and dll is debug, but a writing violation when program is debug and dll is release.</p> <p>What the function is supposed to do is just call push_back("x") a few times with different strings.</p> <p>It doesn't seem to be totally impossible to use a debug dll in a release config program or all the functions of type 1 also wouldn't work, so it seems to have something to do with vector or string class. </p> <p>Anyone have any idea how to solve this or is using two executables with different configurations my only choice?</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. This table or related slice is empty.
    1. USDanielAbele
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POdll in debug mode, calling program in release mode (and vice versa)
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POdll in debug mode, calling program in release mode (and vice versa)
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POdll in debug mode, calling program in release mode (and vice versa)
      1. This table or related slice is empty.
      1. VTUpMod
    1. COPlease give the compiler options that you use for both configurations. For example, it's possible that each configuration uses a different default calling convention (or some other option that makes them incompatible).
      singulars
      1. POdll in debug mode, calling program in release mode (and vice versa)
      1. UScdhowie
    2. COYou could turn off iterator debugging to make them compatible. My doctor's advice when it hurts like that is however `just don't do that`.
      singulars
      1. POdll in debug mode, calling program in release mode (and vice versa)
      1. USHans Passant
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload