Hi,
Bug report is oke. It would be really interesting to know why the USR1 signal
comes in as well as INT. I'm not familiar enough with the specifics of
Tshark-dumpcap communications to know what's going on here. The bug report
should help others understand and evaluate your patch.
Thanx,
Jaap
Gerald Combs wrote:
Sake Blok wrote:
On Thu, Jul 24, 2008 at 09:47:12AM -0700, Gerald Combs wrote:
I was planning on releasing 1.1.0 and 1.0.3 once bug 2675 has been fixed.
Would it be possible to build 1.1.x with MSVC2005EE? That way people
can compile their plugins on windows
Graham Bloice wrote:
> Gerald Combs wrote:
>> Sake Blok wrote:
>>
>>> On Thu, Jul 24, 2008 at 09:47:12AM -0700, Gerald Combs wrote:
>>>
I was planning on releasing 1.1.0 and 1.0.3 once bug 2675 has been fixed.
>>> Would it be possible to build 1.1.x with MSVC2005EE? That wa
Hi,
I've had this build failure for the past few days. I haven't looked at it
deeply, but I don't understand how the exception stuff is working.
packet-infiniband.c: In function `parse_PAYLOAD':
packet-infiniband.c:806: warning: variable 'next_tvb' might be clobbered by
`longjmp' or `vfork'
make
I think it's might be a fake. next_tvb is considered volatile...
because dissector_try_port() does not specify the argument as constant
so the compiler thinks it might change while popping the stack on a
longjmp.
Hi, does the attached patch gets rid of the warning?
Luis
On Mon, Aug 4, 2008 at 1:
On Mon, Aug 4, 2008 at 1:19 PM, Luis EG Ontanon <[EMAIL PROTECTED]> wrote:
> I think it's might be a fake. next_tvb is considered volatile...
> because dissector_try_port() does not specify the argument as constant
> so the compiler thinks it might change while popping the stack on a
> longjmp.
>
On Aug 4, 2008, at 6:03 AM, Martin Mathieson wrote:
> Unfortunately not. I can't see what is different between this case
> and the one in the built-in packet-ethertype.c which may have been
> used as a template in part for the plugin packet-infiniband.c.
packet-ethertype.c has
tvbu
On Mon, Aug 4, 2008 at 4:23 PM, Guy Harris <[EMAIL PROTECTED]> wrote:
>
> On Aug 4, 2008, at 6:03 AM, Martin Mathieson wrote:
>
> > Unfortunately not. I can't see what is different between this case
> > and the one in the built-in packet-ethertype.c which may have been
> > used as a template in p
On Aug 4, 2008, at 8:48 AM, Martin Mathieson wrote:
> ukeng7 martinm main : cat /proc/cpuinfo
> processor : 0
> vendor_id : GenuineIntel
> cpu family : 15
> model : 4
> model name : Intel(R) Pentium(R) 4 CPU 2.40GHz
No more registers than the Ubuntu buildbot, and
On Mon, Aug 4, 2008 at 5:16 PM, Guy Harris <[EMAIL PROTECTED]> wrote:
>
> On Aug 4, 2008, at 8:48 AM, Martin Mathieson wrote:
>
> > ukeng7 martinm main : cat /proc/cpuinfo
> > processor : 0
> > vendor_id : GenuineIntel
> > cpu family : 15
> > model : 4
> > model name
On Mon, 04 Aug 2008 11:29:54 +0200, Jaap Keuter <[EMAIL PROTECTED]>
wrote:
> That was talk about c-ares as replacement for adns. It came out on top of
> my
> preference list (further candidates: UDNS and posadis). I have had no
time
> to
> investigate this any further, let alone start design/implem
Preety quickly in relative terms...
DJB pointed out the vulnerability back in July 2001... that would be
more than 7 years (http://cr.yp.to/djbdns/forgery-cost.txt).
\Lego
On Mon, Aug 4, 2008 at 7:08 PM, Gerald Combs <[EMAIL PROTECTED]> wrote:
> On Mon, 04 Aug 2008 11:29:54 +0200, Jaap Keuter <
On Mon, 2008-08-04 at 17:37 +0100, Martin Mathieson wrote:
> On Mon, Aug 4, 2008 at 5:16 PM, Guy Harris <[EMAIL PROTECTED]> wrote:
> If volatile fixes the problem, that's the right fix; go ahead
> and
> check that in.
> Done, thanks.
Thanks for sorting it out guys, I ha
The Buildbot has detected a new failure of Windows-XP-x86 on Wireshark
(development).
Full details are available at:
http://buildbot.wireshark.org/trunk/builders/Windows-XP-x86/builds/4650
Buildbot URL: http://buildbot.wireshark.org/trunk/
Buildslave for this Build: windows-xp-x86
Build Reason
Abhik Sarkar wrote:
> Hello Ben,
>
> Please follow the instructions here
> (http://www.wireshark.org/docs/wsdg_html_chunked/ChSrcContribute.html#ChSrcSend)
> to make sure that your contribution is tracked properly and not lost.
Done:
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=2770
Than
15 matches
Mail list logo
