Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Since you have already turned off the SSE instruction generation in the compiler, the problem is in one of the static libraries. To narrow it down, basically you have 2 ways go:</p> <ol> <li>Disassemble the .lib or .obj files you are linking to. It is not actually an easy solution unless you happen to have access to specialized tools. Generally, disassembly is a very complex process since the tool has to figure out all the execution paths in the code without actually running it. It does it to separate the data from the code. The best tool for such tasks is <a href="http://www.hex-rays.com/idapro/" rel="nofollow">IDA Pro</a>. After disassembly you can search for the SSE instructions either by writing a macro inside IDA Pro or exporting the results to text files and just using grep.</li> <li>A simpler approach is to run the program and find out where it crashes. You'll need two things to continue: finding out the address of the instruction that causes the crash and a "map file" to find out where it belongs to. The latter is simple: in Visual studio, you have to set the compiler AND the linker debug options to generate a map file. This file will basically tell you the address of all and every function in the executable file. Finding the crash address is usually easy as Windows will prompt you and says something like <em>Application error The instruction at "0x635de077"...</em>. You use that address and look at the map file to see in which function it belongs. Alternatively, you can run the program inside a debugger. When program crashes, the debugger shows you where program has stopped.</li> </ol> <p>edit: Another method to get a disassembly of a .lib files is to use the <a href="http://support.microsoft.com/kb/177429" rel="nofollow">DUMPBIN</a> utility that comes with Visual Studio. Also, the minidump method suggested by STATUS_ACCESS_DENIED is an excellent idea.</p>
    singulars
    1. This table or related slice is empty.
    1. POTracking down which dependency contains SSE instructions
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USAlefSin
    1. USAlefSin
    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. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COI'm a great fan (and customer) of IDA Pro, but I think it's overkill for the task at hand. Any half-way sophisticated diassembler library will do. Also I like your second approach better as it will yield a more accurate result in less time. +1 for that.
      singulars
      1. PO
      1. US0xC0000022L
    2. COActually to add to point 2: it would also be possible to take a minidump when it crashes (even at the customer site) and then analyze the minidump to see that. I.e. post-mortem which is better suited.
      singulars
      1. PO
      1. US0xC0000022L
    3. COYes, the first solution is truly n overkill. I just mentioned it since the other answer just briefly suggested that. Although IDA Pro used to have free version that might be enough for this task. In general, it is good for programmers who deal with low-level code to get used to look at the disassembly of their code.
      singulars
      1. PO
      1. USAlefSin
 

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