|
From: John C. <j.c...@ar...> - 2004-09-22 01:24:19
|
I'm trying to use the PowerPC port of Valgrind on a development system we have for an embedded product. This system has 128MB (we may be able to increase this if needed) and no swap area. Our application typically takes about 30MB for code and data. When I tried running a test (on an even smaller test application) I get an error related to allocated the shadow memory. I found the code for sizing an allocating (using mmap calls) these memories in Valgrind. I tried making them smaller, but still had some issues (I don't know about how those allocated areas are used so it's no surprise it failed). So the question is, is there anything I can do to make Valgrind work in this environment? We can maybe increase RAM, probably not add swap (kernel issues) and I'm willing to tweak valgrind code if needed. Any ideas?? Thanks much for any help! John j.c...@ar... CONFIDENTIALITY NOTICE: This email, together with any attachments, is intended only for use by Aristos Logic Corporation and the individual(s) to which it is addressed and may contain information that is privileged, confidential or exempt from disclosure. If you are not the intended recipient, you are hereby notified that any dissemination, distribution, or copying of this email, or any attachment, is strictly prohibited. If you have received this email in error, please notify Aristos Logic Corporation by sending an email to sy...@ar... and delete this email, along with any attachments, from your computer. Thank you. |
|
From: Nicholas N. <nj...@ca...> - 2004-10-08 14:28:05
|
On Tue, 21 Sep 2004, John Clinton wrote: > I'm trying to use the PowerPC port of Valgrind on a development system we > have for an embedded product. This system has 128MB (we may be able to > increase this if needed) and no swap area. Our application typically takes > about 30MB for code and data. When I tried running a test (on an even > smaller test application) I get an error related to allocated the shadow > memory. I found the code for sizing an allocating (using mmap calls) these > memories in Valgrind. I tried making them smaller, but still had some > issues (I don't know about how those allocated areas are used so it's no > surprise it failed). > > So the question is, is there anything I can do to make Valgrind work in this > environment? We can maybe increase RAM, probably not add swap (kernel > issues) and I'm willing to tweak valgrind code if needed. Any ideas?? Unfortunately, I think it would be really hard to squeeze Valgrind into such a small amount of memory. It just wasn't designed for that. N |