corruption

I'm trying to import a large subversion repository into git using git-svn (so that I can work in git but still dcommit to subversion from time to time). After importing more than 4000 revisions I'm now getting the following error whenever I run git svn fetch or git svn rebase , which I don't manage to get rid of: $ git svn fetch error: invalid object 100644 1f2....742 for 'src/path/.../file.cs' fatal: git-write-tree: error building trees write-tree: command returned error: 128 What I've tried so far: git fsck --full doesn't report anything, neither does git fsck --unreachable or git fsck --no

I'm debugging some random crash bugs, but actually very difficult to go deep into. Because when i open crash dump, only find one error: 0:000> .exr -1 ExceptionAddress: 00000000 ExceptionCode: 80000003 (Break instruction exception) ExceptionFlags: 00000000 NumberParameters: 0 Actually i haven't set any hard-code breakpoint in code, so i search about this exception in google, some people said this exception may be caused by heap corruption. So my question is, Is there any other reason why cause this exception, except hard-code breakpoint, manual breakpoint while debugging, heap corruption?

Guys, could you please recommend a tool for spotting a memory corruption on a production multithreaded server built with c++ and working under linux x86_64? I'm currently facing the following problem : every several hours my server crashes with a segfault and the core dump shows that error happens in malloc/calloc which is definitely a sign of memory being corrupted somewhere. Actually I have already tried some tools without much luck. Here is my experience so far: Valgrind is a great(I'd even say best) tool but it slows down the server too much making it unusable in production. I tried it on

My Program.cs file was working fine this afternoon. I closed Visual Studio (VS2013 Express) and shut down my computer. Then this evening I turned the computer on again and Program.cs now looks like this: f£óö'ûRÏ>•]|êêlÇPš—·õGÉ+s qÖY®ÓÇN­Ž9¯€8ï,? óQwÕ®Åy„Ùrsb^ ƒoÏEl?Qäº6z¹ Ü -³‡kwÎR®Q| €s᪠å²!dKË*:ÀyÉÿ?l ­Ã&Š‚Ëð.Š›ï,²©“Óü@q:VªÐMãҟ岂¡ËÀÌ<öò§-ž‹66‚j$+”tVeÃÛSVÿ Ïr£pÉ'äûèk0Iœ¾Y/HÅ;vþ DãjÊÕIÿóõ‘>¤¶ËLw¬,‚ÓHï’$t‡³Ywõ2ŽHíg3É·HVß{fÄèÄKõ™>§ïä ŽíC}r^— x èd’—X÷§º~qXPk# etc. Any ideas on how to recover it? I tried running Recuva, but that didn't work. There is no copy in the Backup Files folder for

I'm writing a java file-transfer app, and i have some troubles with deserialisation myself-defined class Message from Datagramms. Other topics at StackOverflow has similar issues, but i didn't found something helpful from there, so i'm sorry in advance if i missed it. so, class Message is: import java.io.Serializable; public class Message implements Serializable { private static final long serialVersionUID = 1L; private int segmentID; private byte[] packet; private int bytesToWrite; public Message(){ segmentID = -1; } public Message(int segmentID, byte[] packet, int bytesToWrite) { this

I got an error on my C program on runtime. I found some stuff about "double free or corruption" error but nothing relevant. Here is my code : void compute_crc32(const char* filename, unsigned long * destination) { FILE* tmp_chunk = fopen(filename, "rb"); printf("\n\t\t\tCalculating CRC..."); fflush(stdout); Crc32_ComputeFile(tmp_chunk, destination); printf("\t[0x%08lX]", *destination); fflush(stdout); fclose(tmp_chunk); printf("\t[ OK ]"); fflush(stdout); } It seems the fclose(tmp_chunk); raises this glibc error : *** glibc detected *** ./crc32: double free or corruption (out): 0x09ed86f0 ***