|
From: Alex B. <al...@tr...> - 2006-09-06 17:28:37
|
On Wed, 2006-09-06 at 17:54 +0100, Alex Bennee wrote: > So I think I have a bug in my code, unfortunately I'm not sure if its > exposed a bug in valgrind as well. It seems odd that I'm seeing a bad > read in the linker code. Further to my previous comments I think it may well be a valgrind bug. I instrumented my code with a few printfs and I can see where the lock value get written and what gets read back. I also added a client side check to the getPid() function to see if it was getting trampled. The output was something like: setPid tc=0x424e170 pid=15979 getLock tc=0x424e170, pid=15979 getLock tc=0x424e170, pid=15979 getLock tc=0x424e170, pid=15979 getLock tc=0x424e170, pid=15979 getLock tc=0x424e170, pid=15979 getLock tc=0x424e170, pid=15979 getLock tc=0x424e170, pid=15979 getLock tc=0x424e170, pid=15979 getLock tc=0x424e170, pid=15979 ==15979== Warning: set address range perms: large range 198787072 (defined) getLock tc=0x424e170, pid=0 Before locking up. No client requests fired. The "set address range perms" is interestingly placed. Whats it mean? > > Any ideas? > > -- > Alex, homepage: http://www.bennee.com/~alex/ > Ask not for whom the tolls. > > > ------------------------------------------------------------------------- > Using Tomcat but need to do more? Need to support web services, security? > Get stuff done quickly with pre-integrated technology to make your job easier > Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo > http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 > _______________________________________________ > Valgrind-users mailing list > Val...@li... > https://lists.sourceforge.net/lists/listinfo/valgrind-users -- Alex Bennee - al...@tr... Your job is being a professor and researcher: That's one hell of a good excuse for some of the brain-damages of minix. (Linus Torvalds to Andrew Tanenbaum) |