在目录中创建应用程序快捷方式(Creating application shortcut in a directory)

 如果您损坏堆或免费存储，例如通过双重释放（或双重删除）指针，访问指针，Segfaults似乎来自其他经过良好调试的库（甚至来自标准库！）已经释放（或删除），释放（或删除）未分配的指针，使用删除，你应该使用delete []，反之亦然等。 
 
 这种崩溃通常发生在完全不同的地方，并且发生错误的时间和地点完全不同。 如果你有多个线程共享的矩阵以外的变量，并且你有一个竞争条件，例如，导致你双重删除共享变量，这可能会破坏免费存储，然后导致升级矩阵内部崩溃码。 
 
 您应该通过valgrind之类的工具运行代码，以尝试追踪堆/免费存储损坏。 

Segfaults can appear to arise from other, well-debugged libraries (or even from the standard library!) if you corrupt the heap or the free store, for example by double-freeing (or double-deleting) a pointer, accessing a pointer that was already freed (or deleted), freeing (or deleting) a pointer that was not allocated, using delete where you should have used delete[] or vice-versa, etc. 
 
This crash will often happen in a completely different place and at a totally different time from when and where the error occurred. If you have variables other than the matrices shared among multiple threads, and you have a race condition that, for example, causes you to double-delete the shared variable, this could corrupt the free store and later cause a crash inside of the boost matrix code.
 
You should run your code through a tool like valgrind to try to track down the heap/free store corruption.