this is the code which calls sendto - I added memset before init variables
at line 3, didn't help.
1. UMI_REQ_INFO * pUmiReq;
2. unsigned int reqBufSize;
3.
4.
5. pUmiReq = (UMI_REQ_INFO *)pBuf;
6. pUmiReq->cmd = cmd;
7. pUmiReq->srcId = pSrcCtx->myId;
8. pUmiReq->reqOpt = reqOpt;
9. pUmiReq->reqId = reqId;
10. pUmiReq->req = 1;
11.
12. if (sendto (pSrcCtx->sockFd, pUmiReq, reqBufSize,
13. 0, (struct sockaddr *) &destId,
sizeof(UMI_COMP_ID)) == -1)
14. {
On Tue, Jan 19, 2010 at 9:27 AM, Ashley Pittman <[email protected]>wrote:
>
> The error shown is nothing to do with malloc, you are passing uninitialised
> data to the kernel in the sendto() system call.
>
> Ashley,
>
> On 19 Jan 2010, at 14:24, Vasanta wrote:
>
> I looked into adpModuleDebug which was shown by stack trace - I don't
> have any mallocs except printfs/vsnprintf/sprintf (to log msgs into syslog)
>
> On Mon, Jan 18, 2010 at 4:49 PM, Ashley Pittman <[email protected]>wrote:
>
>>
>> On 18 Jan 2010, at 21:42, Vasanta wrote:
>>
>> Thanks Ashley. on my target I don't have GDB, I have to copy GDB from
>> host, also I have to compile my code with -g option to debug that routine
>> with gdb to findout where exactly it is.
>>
>>
>> You don't need to have gdb installed for Valgrind to work, it just uses
>> the same debug info from the application. If gdb can show you line numbers
>> valgrind should also be able to.
>>
>> This is the first time I using this valgrind, I want to confirm for
>> these few lines below, always the error is: line below "sendto" line right,
>> which is pointed with red color text below?.
>>
>>
>> This is the stack trace where uninitialised data is passed into the
>> kernel.
>>
>> ==2107== Syscall param socketcall.sendto(msg) points to uninitialised
>> byte(s)
>>
>> ==2107== at 0x43B731E: sendto (in /lib/libpthread-2.5.so)
>> <-----
>> Pthread routine
>>
>> ==2107== by 0x439A019: adpModuleDebug (in
>> /pfrm2.0/lib/libi386adaptos.so) <--- My module memory corruption
>>
>> ==2107== by 0x8059C4D: cacStatsUpdate (in /pfrm2.0/bin/cacd)
>>
>> ==2107== by 0x80524A4: cacdRun (in /pfrm2.0/bin/cacd)
>>
>> ==2107== by 0x805286F: main (in /pfrm2.0/bin/cacd)
>>
>> ==2107== Address 0xbefd44cc is on thread 1's stack
>>
>>
>
>
------------------------------------------------------------------------------
Throughout its 18-year history, RSA Conference consistently attracts the
world's best and brightest in the field, creating opportunities for Conference
attendees to learn about information security's most important issues through
interactions with peers, luminaries and emerging and established companies.
http://p.sf.net/sfu/rsaconf-dev2dev
_______________________________________________
Valgrind-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/valgrind-users
