Wireshark · Wireshark-dev: [Wireshark-dev] C++ program usig "editcap"

["SOLTANI FATEN" <Faten.Soltani@xxxxxxxxxxxxxxxxxx>]

Hello all,
I'll need to use the EDITCAP to convert files from ASCII format to pcap format, I need a help about writing a C++ program, where I call the editpcap function, and where the input file must be located(in the same folder as the function editpcap?).
Thanks for any help


-----Message d'origine-----
De : wireshark-dev-bounces@xxxxxxxxxxxxx [mailto:wireshark-dev-bounces@xxxxxxxxxxxxx] De la part de wireshark-dev-request@xxxxxxxxxxxxx
Envoyé : jeudi 19 mars 2009 20:00
À : wireshark-dev@xxxxxxxxxxxxx
Objet : Wireshark-dev Digest, Vol 34, Issue 45

Send Wireshark-dev mailing list submissions to
	wireshark-dev@xxxxxxxxxxxxx

To subscribe or unsubscribe via the World Wide Web, visit
	https://wireshark.org/mailman/listinfo/wireshark-dev
or, via email, send a message with subject or body 'help' to
	wireshark-dev-request@xxxxxxxxxxxxx

You can reach the person managing the list at
	wireshark-dev-owner@xxxxxxxxxxxxx

When replying, please edit your Subject line so it is more specific
than "Re: Contents of Wireshark-dev digest..."


Today's Topics:

   1. Re: XML parsing (Jeff Morriss)
   2. ESP decoding capabilities (Vincent Helfre)
   3. g_snprintf() and sizeof (Guy Harris)


----------------------------------------------------------------------

Message: 1
Date: Thu, 19 Mar 2009 10:52:23 -0400
From: Jeff Morriss <jeff.morriss.ws@xxxxxxxxx>
Subject: Re: [Wireshark-dev] XML parsing
To: Developer support list for Wireshark <wireshark-dev@xxxxxxxxxxxxx>
Message-ID: <49C25C27.9030005@xxxxxxxxx>
Content-Type: text/plain; charset=UTF-8; format=flowed



Abhik Sarkar wrote:
> Hi Everyone,
> 
> This is a question specifically to the core developers. Would it be OK 
> to use the GMarkupParser facility which is provided by the latest glib 
> that is part of the required libraries for the development version? I 
> want to use it to read XML configuration files for a generally available 
> dissector.

Define "latest."  (I looked through the GLIB documentation and their 
list of symbols new to each release and at least some of the markup 
functions have been around for a while.)


------------------------------

Message: 2
Date: Thu, 19 Mar 2009 17:25:36 +0100
From: "Vincent Helfre" <vincent.helfre@xxxxxxx>
Subject: [Wireshark-dev] ESP decoding capabilities
To: wireshark-dev@xxxxxxxxxxxxx
Message-ID: <20090319162536.102650@xxxxxxx>
Content-Type: text/plain; charset="iso-8859-1"

Hi all,
I used once in a while the ESP decoding capability on Wireshark, and it seems it does not work anymore. Could anyone familiar with IPSec help me have a look at that? I raised the bug report 2943 and attached a log with the keys, so it is possible to test it. It used to work on version 0.99.8 but does not on version 1.1.2 and later.

BRs,
Vincent 
-- 
Psssst! Schon vom neuen GMX MultiMessenger geh?rt? Der kann`s mit allen: http://www.gmx.net/de/go/multimessenger01


------------------------------

Message: 3
Date: Thu, 19 Mar 2009 11:12:03 -0700
From: Guy Harris <guy@xxxxxxxxxxxx>
Subject: [Wireshark-dev] g_snprintf() and sizeof
To: wireshark-dev@xxxxxxxxxxxxx
Message-ID: <09DE2876-F92F-43A4-8E16-DF84E23AFCB2@xxxxxxxxxxxx>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes


On Mar 19, 2009, at 10:44 AM, wmeier@xxxxxxxxxxxxx wrote:

> -As suggested by Jakub Zawadzki: use sizeof(...) rather than a  
> numeric constant in various places;

Warning: g_snprintf()'s function signature has an annoying botch in it  
- the size argument is a gulong, not a gsize.

Not a problem in the UN*X and Windows ILP32 environment and in the  
UN*X LP64 environment, but it causes the Microsoft compiler to  
(correctly) warn about a conversion from a 64-bit integer to a 32-bit  
integer in the Windows LLP64 environment.  Cast sizeof - or any other  
size_t value - to (gulong) before passing it as the length argument to  
g_snprintf().


------------------------------

_______________________________________________
Wireshark-dev mailing list
Wireshark-dev@xxxxxxxxxxxxx
https://wireshark.org/mailman/listinfo/wireshark-dev


End of Wireshark-dev Digest, Vol 34, Issue 45
*********************************************