64-bit

问题 I'm trying to build a C program on Matlab 2012a, through the command: mex mat_trans2.c And I'm getting this error: /usr/bin/ld: cannot find -lstdc++ collect2: ld returned 1 exit status mex: link of ' "mat_trans2.mexa64"' failed. Error using mex (line 206) Unable to complete successfully. Some time ago I was able to build .c files, I don't know what is happening now! Maybe something has changed after a system upgrade on my Kubuntu 12.04 64 bit. Is there someone who know how to solve this?

问题 I have compiled ruby 64 bit on an AIX Box. There doesn't seem to be any issue except when I use some specific regular expressions in my code. Here is an example: /([0-9]){1000}/.match("2") results in: RegexpError: too big quantifier in {,}: /([0-9]*){1000}/ When I try reducing the number of repetitions, it seems to work. I tried digging into the ruby code. But could not understand the reason. Is this some dependency or restriction that we have in AIX/64 bit ruby? Thanks in advance :) 回答1: I

问题 Is it possible yet to build 32bit and 64bit 'fat' binaries for iOS? My understanding was that this was coming down the line but I can't see an obvious way to do it in the latest update to Xcode? I want my application to run in 64bit mode on 5S and 32bit on 5 and below (obviously), I did read the docs: Applications can now target iOS 5.1.1 and later while building for 64-bit using the “Standard architecture (including 64-bit)” build setting. This produces an Archive for the App Store with a

问题 I have a 64bit program that works with VirtualBox COM interface and implements a frontend for the virtual machine. Recently I started getting weird An invalid or unaligned stack was encountered during an unwind operation exceptions and I wanted to at least understand the causes of this. As I understand the stack needs to be 16byte aligned so, I presume unaligned stack pointer likely to cause this. But the thing is, since all my program does is implement a couple of COM interfaces using the

问题 I'm running Netbeans on 64-bit Windows 8, with JDK 1.7_25 (64-bit), following the instructions for the Beginning JNI with NetBeans (https://netbeans.org/kb/docs/cnd/beginning-jni-linux.html) The instructions are for linux, but the principle is the same for Windows I believe (generating a .dll file instead of .so, using win32 includes in the JDK, etc) I have Cygwin64 installed as well as Cygwin32. Using Cygwin64, I'm able to generate a 64-bit DLL from my C/C++ Dynamic Library project. However,

问题 I am currently implementing an ASP.Net application which is using GDI+ to do server-side rendering. First versions were dependent on a 32 bits unmanaged component, so all the managed assembly were compiled for x86 platform. Lastly I got rid of this dependency and am now able to set the target platform to AnyCPU. Since the application can potentially be used to handle a lot of data, being able to run it in 64 bits may be useful. However I read there is a performance decrease when using GDI+ on

问题 This error is present in both Debug/Release. So the original problem was that it had 32 bit library that I did not link to 64 version of it. (Previous version of this question) I fixed that. And application works on Windows Server Standard 2008R2 x64. I tried running application on Windows Server Enterprise but got above (title) mentioned error message. Dependency walker says "Modules with different CPU types were found" and for some reason it seems its linking incorrectly to 32 bit library,

问题 I just tried to use devIL and ULIT to help me with opengl texture loading. However, whenever the program starts, I get the error: "The application was unable to start correctly (0xc000007b). Click OK to close the application." What happened? I'm using the Visual C++ 2010 RC, windows 7 64-bit. 回答1: It may happen if you attempt to run a 64-bit application, but Windows finds only the 32-bit version of some dependent DLL. You can fix this by making sure all the 64-bit dependency DLLs can be found

问题 I'm using VS2008 and the project properties are set for (active) x64 and the weird thing is _WIN64 is not defined and WPARAM and LPARAM are still 32-bit. Should I define _WIN64 manually? If so, where should I put #define _WIN64? Preprocessor setting doesn't seem to work. I'm quite certain it's compiled as x64 because in task manager the exe has no *32 postfix. 回答1: The thing is, _WIN64 is already defined by compiler but the IDE couldn't recognize it. (seemed fixed in VS2010.) The values of

问题 I'm trying to walk a callstack that contains both managed and native frames on a x64 process using StackWalk64. Everything works fine until the first or second managed frame, after which StackWalk64 can't figure out the return address of the frame and fails. I'm using SymFunctionTableAccess64 for the function table access callback and the symbol handler has been initialized with SymInitialize(). Is there some magic I need to do in dbghelp to get it to walk over managed frames correctly?