On Jan 10, 2013, at 7:22 AM, Derek Cole wrote:
> Can you provide a link where I can see the changes you made?
The bug I filed against Valgrind:
https://bugs.kde.org/show_bug.cgi?id=312989
has a patch.
> I thought valgrind had a source code repo viewer for latest patches and stuff
>
Thanks for taking some time to check that out. Can you provide a link where
I can see the changes you made? I thought valgrind had a source code repo
viewer for latest patches and stuff being checked in, but I couldnt find
it. I'd like to take a look at what you did so I can maybe learn how to do
t
On Jan 9, 2013, at 1:34 PM, Guy Harris wrote:
> On Jan 9, 2013, at 1:29 PM, Derek Cole wrote:
>
>> I am not sure whether that is a worthwhile check-in to make for pcap or not.
>
> I'd rather fix valgrind. I'll see if I can beat it into working on Mountain
> Lion,
Well, the top-of-trunk SV
On Jan 9, 2013, at 1:29 PM, Derek Cole wrote:
> Well, after tracking down some of the structures being used in the ioctl
> arguments, and memset() them to zero, I think all of the errors went away
> without the need to write any additional wrappers other than the pselect()
> wrapper. Most of
Well, after tracking down some of the structures being used in the ioctl
arguments, and memset() them to zero, I think all of the errors went away
without the need to write any additional wrappers other than the pselect()
wrapper. Most of those calls were int he bpf-pcap.c file. I am not sure
wheth
Thanks,
That might be enough information for me to get a start on tackling some of
this.
Just for reference, this is the version of valgrind for FreeBSD i've been
working off of
http://wiki.freebsd.org/Valgrind
On Tue, Jan 8, 2013 at 11:32 PM, Guy Harris wrote:
>
> On Jan 8, 2013, at 7:08 PM
On Jan 8, 2013, at 7:08 PM, Derek Cole wrote:
> Thanks for the detailed response. You are correct that was my stack overflow
> post. At the time I posted that I didn't have as clear of an idea of the
> problem, so, casting a wide net.
>
>> Valgrind is complaining about several uninitialized
Hello,
Thanks for the detailed response. You are correct that was my stack
overflow post. At the time I posted that I didn't have as clear of an idea
of the problem, so, casting a wide net.
>Valgrind is complaining about several uninitialized variables, *and* about
"unhandled ioctl 0x20004269 wit
On Jan 8, 2013, at 1:58 PM, Derek Cole wrote:
> I am not sure this is the right mailing list for this or not,
It is. "tcpdump-workers" is actually a combination of:
"tcpdump-users" - users of tcpdump;
"tcpdump-workers" - developers of tcpdump;
"libpcap-users" - "user
Hello,
I am not sure this is the right mailing list for this or not, but if not,
someone can point me in the right direction.
I am trying to debug some software that is using libpcap, with valgrind. I
am not able to get my software to launch, because valgrind is returning the
dump at the bottom
10 matches
Mail list logo
