Bill Meier wrote:
> The specific problem: dumpcap calls capture_loop_start (in capture_loop.c)
> which
> calls capture_opts_log (in capture_opts.c) which then passes a null pointer to
> glog (for iface_descr); glog then causes dumpcap to die
>
> A very quick look suggested I'd need to take
Jeff Morriss <[EMAIL PROTECTED]> writes:
>
>
> I hope so, but it appears to have worked before my change and not after,
> so... I'm a bit nervous.
>
Jeff:
Your intuition is correct. The current version of dumpcap is crashing on Windows
because of a null pointer in capture_opts->iface_descr a
It's compiling OK now, but it's hanging on one of the capture tests.
Jeff Morriss wrote:
> I hope so, but it appears to have worked before my change and not after,
> so... I'm a bit nervous.
>
> Luis EG Ontanon wrote:
>> The question is can winpcap capture on a virtual interface of a virtual
>
I hope so, but it appears to have worked before my change and not after,
so... I'm a bit nervous.
Luis EG Ontanon wrote:
> The question is can winpcap capture on a virtual interface of a virtual
> machine?
>
> I think it is waiting for a click (as it happened already in the past).
>
> I thin
The question is can winpcap capture on a virtual interface of a virtual machine?
I think it is waiting for a click (as it happened already in the past).
I think tests that assume anything being available on the system
should be run with by a special target but not by the "all" target.
Luis
On 8
Gerald Combs wrote:
> Graham Bloice wrote:
>> The buildbot is reporting a permission problem.
>
> It looks like the GUI crashed during the "capture 10 packets" test, and
> Windows popped up the "Wireshark has encountered a problem..." dialog.
> I'll tweak the error reporting settings on the buil
Gerald Combs wrote:
> Graham Bloice wrote:
>> The buildbot is reporting a permission problem.
>
> It looks like the GUI crashed during the "capture 10 packets" test, and
> Windows popped up the "Wireshark has encountered a problem..." dialog.
> I'll tweak the error reporting settings on the buil
Graham Bloice wrote:
> The buildbot is reporting a permission problem.
It looks like the GUI crashed during the "capture 10 packets" test, and
Windows popped up the "Wireshark has encountered a problem..." dialog.
I'll tweak the error reporting settings on the builder.
__
The buildbot is reporting a permission problem.
--
Regards,
Graham Bloice
___
Wireshark-dev mailing list
Wireshark-dev@wireshark.org
http://www.wireshark.org/mailman/listinfo/wireshark-dev
amping
>> Sent: 12 February 2007 04:52
>> To: wireshark-dev@wireshark.org
>> Subject: [Wireshark-dev] Win32 buildbot unhappy while building docs
>>
>> Hi!
>>
>> The buildbot currently has real problems building the
debugging.
Cheers
Doug
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of Ulf Lamping
> Sent: 12 February 2007 04:52
> To: wireshark-dev@wireshark.org
> Subject: [Wireshark-dev] Win32 buildbot unhappy while building docs
>
> Hi!
>
Hi!
The buildbot currently has real problems building the docbook docs and a
look at the logs doesn't indicated to me what the problem is.
Any ideas?
Regards, ULFL
___
Wireshark-dev mailing list
Wireshark-dev@wireshark.org
http://www.wireshark.org/mai
12 matches
Mail list logo
