I have compiled a shared library only..
On Wed, Jul 20, 2011 at 9:39 PM, Joerg Mayer wrote:
> On Wed, Jul 20, 2011 at 04:47:48PM +0530, sagar Guledagudda wrote:
> > I have compiled my dissector in linux and i have a shared library xxx.so.
> > and i have kept in the wireshark-1.4.7/plugins/1.4.7
On Thu, Jul 21, 2011 at 01:32:51AM +0200, Joerg Mayer wrote:
> On Wed, Jul 20, 2011 at 09:28:23PM +0200, Michael T?xen wrote:
> > I guess you have a preferred capture
> > interface, right? We put this interface on the ifaces list, since
> > it is equivalent to specifying it on the command line.
> >
On Wed, Jul 20, 2011 at 09:28:23PM +0200, Michael T?xen wrote:
> I guess you have a preferred capture
> interface, right? We put this interface on the ifaces list, since
> it is equivalent to specifying it on the command line.
> The same problem should occur when you specify interfaces on the comma
On Jul 20, 2011, at 9:41 PM, Joerg Mayer wrote:
> On Wed, Jul 20, 2011 at 09:28:23PM +0200, Michael T?xen wrote:
>> Irene can take a look at this tomorrow . I guess you have a preferred capture
>> interface, right? We put this interface on the ifaces list, since
>> it is equivalent to specifying i
Would it be OK to increase the minimum required version of gtk2 from
2.12 to 2.14? Otherwise we will need to protect more than 110 instances
of gtk_widget_get_window. It would also allow the removal of 49 existing
protections. I don't mind doing this with protection but it will be terrible
for the
On Wed, Jul 20, 2011 at 09:28:23PM +0200, Michael T?xen wrote:
> Irene can take a look at this tomorrow . I guess you have a preferred capture
> interface, right? We put this interface on the ifaces list, since
> it is equivalent to specifying it on the command line.
True:
capture.device: eth0
>
On Jul 20, 2011, at 8:41 PM, Joerg Mayer wrote:
> On Wed, Jul 20, 2011 at 07:39:32PM +0200, Joerg Mayer wrote:
>> I am seeing Gtk-CRITICAL messages, but only if dumpcap has insufficient
>> privileges to capture/list interfaces (see below). I hope that this is
>> not a side effect of my changes :-/
On Wed, Jul 20, 2011 at 07:39:32PM +0200, Joerg Mayer wrote:
> I am seeing Gtk-CRITICAL messages, but only if dumpcap has insufficient
> privileges to capture/list interfaces (see below). I hope that this is
> not a side effect of my changes :-/ How can one go to locate the source
> of such a probl
Hello,
I have fixed most of the struct GtkAllocation access errors when building
with -DGSEAL (all occurences except rtp_player.c).
As I really do not understand what I'm doing here, it would be nice if
someone would be willing to review this, especially whether the call to
gtk_widget_get_allocati
On Jul 20, 2011, at 10:39 AM, Joerg Mayer wrote:
> I am seeing Gtk-CRITICAL messages, but only if dumpcap has insufficient
> privileges to capture/list interfaces (see below).
I'd ask "what happens if you don't have any interfaces at all", but the only
way to get that would probably be to take
Hello,
I am seeing Gtk-CRITICAL messages, but only if dumpcap has insufficient
privileges to capture/list interfaces (see below). I hope that this is
not a side effect of my changes :-/ How can one go to locate the source
of such a problem (in this case it's hopefully somewhere where the
interface
On Wed, Jul 20, 2011 at 04:47:48PM +0530, sagar Guledagudda wrote:
> I have compiled my dissector in linux and i have a shared library xxx.so.
> and i have kept in the wireshark-1.4.7/plugins/1.4.7 but its not getting
> loaded , Do i need to recompile the wireshark source code to make it work. ?
>
I am trying to decrypt a capture of a Zigbee SE device joining to an
ECC-encrypted smart meter (AES-128, 32-bit IP). The device is using
an installation code, so I entered the derived link key into the
Zigbee NWK key list and it looks like the network layer is decrypted
just fine.
The problem I a
> From: Helge Kruse
> Date: Wed, 20 Jul 2011 09:29:47 +0200
>
> Am 19.07.2011 14:23, schrieb Davide Milanesio:
>
> Hi all,
>
> I am trying to make a Wireshark Installer from the latest development
>release (1.7.0), according to Section 2.2.13 of Wireshark Developer's
>Guide.
> Compil
The Buildbot has detected a new failure of Windows-7-x64 on Wireshark
(development).
Full details are available at:
http://buildbot.wireshark.org/trunk/builders/Windows-7-x64/builds/2447
Buildbot URL: http://buildbot.wireshark.org/trunk/
Buildslave for this Build: windows-7-x64
Build Reason:
What is .la file how do we get it?
On Mon, Jul 11, 2011 at 4:16 PM, Ankith Agarwal wrote:
>
> On Mon, Jul 11, 2011, sagar sg said:
>
> > Hi,
> > I have written a dissector plug in in windows and it works fine, now
> i
> > want to compile it in linux to get the .so file, please help me ho
hi,
I have compiled my dissector in linux and i have a shared library xxx.so.
and i have kept in the wireshark-1.4.7/plugins/1.4.7 but its not getting
loaded , Do i need to recompile the wireshark source code to make it work. ?
and i have seen some files with .la extension where as i don hv any s
Am 19.07.2011 14:23, schrieb Davide Milanesio:
Hi all,
I am trying to make a Wireshark Installer from the latest development
release (1.7.0), according to Section 2.2.13 of Wireshark Developer's
Guide.
Compiling and testing on Win XP.
Unfortunately, after the source is correctly compiled and al
18 matches
Mail list logo
