|
From: Nicholas N. <nj...@cs...> - 2005-08-08 14:36:39
|
On Mon, 8 Aug 2005, krishna kumar madhariwar wrote: > my programming is crashing immediately when do memcpy .. I'm not surprised -- look at all those error messages! Lucky you've got Valgrind to tell you what the problem is. Seriously, do you expect a useful response to your email? Put yourself in someone else's shoes for a minute. (Actually, do it as often as you can, it's amazing what you'll learn.) How are we, the readers of this list, supposed to help you? You haven't asked a specific question, or given us any relevant pieces of source code. You haven't said what it is you don't understand about Valgrind's output. You haven't given a useful subject line to the email. You've just posted some Valgrind output and said "please help!". This is useless, and I'm not surprised you haven't received any responses. (I normally wouldn't reply to an email like this, but we've received a few on this list recently like this one, so I thought it might be worth reminding people how these things work.) Try reading the links mentioned on www.valgrind.org/support/bug_reports.html for information on how to ask questions properly. We're willing to help you, but the easier you make it for us, the more likely it is you'll get a useful response. One thing I will say: it's unfortunate that Valgrind is crashing, but it looks like you've overrun the end of a heap block far enough that you're corrupting the heap block's metadata which is (not surprisingly) crashing Valgrind's allocator. Nick |