On Fri, Feb 12, 2016 at 9:35 AM, FIXED-TERM Scholz Tobias (DC-IA/EAI) <
[email protected]> wrote:

> Hello.
>
> In my dissector, a user has to define a network path, in which some text
> files are saved. Therefore I am using the function
> ‘prefs_register_directory_preference( )’ to get the path to a folder.
> I also searched for the difference between UNIX and WIN network path names
> and noticed, that WIN uses the backslashes (e.g.: ‘D:\Development\...’ )
> and UNIX the slashes (e.g.: ‘…/Development/…’ ).
>
> Before using Wireshark 2.1.0 everything was fine with this functionality.
> The path was correctly been given to the program, for example for my
> windows pc ‘D:\Development\files’ (backslashes). Since I have upgraded my
> patch up to Wireshark 2.1.0, I still use the same function, but in
> comparison, Wireshark now returns for the same machine
> ‘D:/Development/files’ (slashes).
> Even the protocol ‘MATE’ also uses the preference functionality , to
> define the path to a special file. But also there, the same problem appears.
>
> For explanation:
> I am using this path, to find several different files in this folder,
> which are including important information for my dissector. Therefore I add
> (depending on the operating system)  \<filename> for WIN or /<filename> to
> open the file and to search for the information in it. But getting the path
> ‘D:/Development/files’ from Wireshark I’m adding for my windows pc
> \<filename>, which gives me the total path to the file
> ‘D:/Development/files\<filename>’.
>
> Does someone have the same problems and a solution for it or is there
> anything I forgot due to the new version of Wireshark?
>
>
>
Hi Tobias,

It look like a bug... can you open a issue on bugtracker ? (
https://bugs.wireshark.org )

Cheers

> T. Scholz
>
>
> ___________________________________________________________________________
> Sent via:    Wireshark-dev mailing list <[email protected]>
> Archives:    https://www.wireshark.org/lists/wireshark-dev
> Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
>              mailto:[email protected]
> ?subject=unsubscribe
>
___________________________________________________________________________
Sent via:    Wireshark-dev mailing list <[email protected]>
Archives:    https://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
             mailto:[email protected]?subject=unsubscribe

Reply via email to