You should commit this change via gerrit. I think it is ok but you should also
check in your code if a call is valid or not by checking for a loaded trace.
Regards, Roland
> Am 27.11.2015 um 23:52 schrieb Paul Offord :
>
> Hi,
>
> If you call plugin_if_goto_frame when there is no capture f
Hi,
If you call plugin_if_goto_frame when there is no capture file loaded you get
an Protection Exception in cf_goto_frame (in file.c).
The code is:
gboolean
cf_goto_frame(capture_file *cf, guint fnumber)
{
frame_data *fdata;
fdata = frame_data_sequence_find(cf->frames, fnumber); // ***
Hello Alexis,
Thank you, this is what I actually did!
Bye,
jo
2015-11-27 22:48 GMT+01:00 Alexis La Goutte :
>
>
> On Wed, Nov 11, 2015 at 9:49 AM, Jo wrote:
>>
>> Hello Chris,
>>
>> I really like this idea but IIRC not the complete API is exposed to
>> plugins and so str_to_ip and str_to_ip6 ar
On Wed, Nov 11, 2015 at 9:49 AM, Jo wrote:
> Hello Chris,
>
> I really like this idea but IIRC not the complete API is exposed to
> plugins and so str_to_ip and str_to_ip6 are not available in a
> standard installation for plugins (they are not included in the
> libwireshark.def file which I do n
On Nov 27, 2015, at 7:09 AM, Tim Furlong wrote:
> Sorry if I'm just missing something, but would editcap itself do the job?
>
> editcap
>
> should read your Wildpackets file and produce a pcapng file; add a "-F pcap"
> for pcap format instead.
...as long as it's not an AiroPeek capture o
Sorry if I'm just missing something, but would editcap itself do the job?
editcap
should read your Wildpackets file and produce a pcapng file; add a "-F
pcap" for pcap format instead.
Can't speak to performance, but I'd be surprised if editcap were
significantly slower than libwiretap itself f
Hello,
Ok, I can see it now. It seems to I was on dark side of the force I
did not see my combobox. Sorry about the confusion. Works for me.
On 23 November 2015 at 22:12, Guy Harris wrote:
>
> On Nov 23, 2015, at 2:59 AM, Michal Labedzki
> wrote:
>
>>>*For meta-filters, remove the fil
On 27 November 2015 at 09:08, Paul Offord wrote:
> Thanks Alexis.
>
>
>
> I’ll try to do as you asked, but as I hadn’t heard of gerrit until you
> responded it may take me some time L
>
>
>
>
>
Paul,
Instructions for submissions are on the wiki:
https://wiki.wireshark.org/Development/SubmittingP
Thanks Roland,
I’ll review your feedback and look a bit further.
For the record, I’m trying to build this for the Qt environment and the source
is v2.1.0rc0-615-gf38bd00 from master
Thanks and regards…Paul
From: wireshark-dev-boun...@wireshark.org
[mailto:wireshark-dev-boun...@wireshark.org]
Hi
I do not have anything standing in front of my callbacks, therefore I would
remove WS_DLL_PUBLIC_DEF completely. It is not necessary in your case.
Secondly, if you are using the latest git source of Wireshark or the 2.0
source, the correct prototype for the callback would be:
void menu_cb(ext_
2015-11-27 10:09 GMT+01:00 POZUELO Gloria (BCS/PSD) :
> I think I’ve just realized which is the problem. Could it be that my paths
> are …/Debug/… ? I’m going to try to build it to RelWithDebInfo…
>
Yes it's probably related. Ensure to execute all projects with the same
configuration.
>
> *From
I think I’ve just realized which is the problem. Could it be that my paths are
…/Debug/… ? I’m going to try to build it to RelWithDebInfo…
From: wireshark-dev-boun...@wireshark.org
[mailto:wireshark-dev-boun...@wireshark.org] On Behalf Of POZUELO Gloria
(BCS/PSD)
Sent: Friday 27 November 2015 1
Thanks Alexis.
I’ll try to do as you asked, but as I hadn’t heard of gerrit until you
responded it may take me some time ☹
From: wireshark-dev-boun...@wireshark.org
[mailto:wireshark-dev-boun...@wireshark.org] On Behalf Of Alexis La Goutte
Sent: 26 November 2015 13:27
To: Developer support list
Hi Pascal,
Here is the qt-dll-manifest.nsh content:
#
# Automatically generated by windeployqt-to-nsis.ps1
#
# Qt version 5.4.2
#
File "F:\Development\run\Debug\icuin53.dll"
File "F:\Development\run\Debug\icuuc53.dll"
File "F:\Development\run\Debug\icudt53.dll"
File "F:\Development\run\Debug\Qt5C
2015-11-27 9:45 GMT+01:00 Bálint Réczey :
> Hi Dario,
>
> You did not write the platforms you want to support, but in case it is just
> Ubuntu/Debian there are pre built wiretap headers and librerary for your
> consumption :-):
> https://packages.debian.org/unstable/libwiretap-dev
>
> It releasing
Hi Dario,
You did not write the platforms you want to support, but in case it is just
Ubuntu/Debian there are pre built wiretap headers and librerary for your
consumption :-):
https://packages.debian.org/unstable/libwiretap-dev
It releasing the new software under GPL2+ we can integrate it to wire
2015-11-27 8:11 GMT+01:00 POZUELO Gloria (BCS/PSD)
:
> Hello everyone,
>
> I'd like to ask you about wireshark packaging. I'm trying to build a x64
> version and when I execute these commands:
>
> > msbuild /m /p:Configuration=RelWithDebInfo nsis_package_prep.vcxproj
>
> > msbuild /m /p:Configura
The scenario I was figuring out was to have a software that wants to
leverage the libwiretap features. The user could build wiretap in the
original wireshark dir, as normal. Then it could compile/link the new
software againts the compiled lib. That implies a process made by hand and
not semi-automa
18 matches
Mail list logo
