On 2013-02-06 22:52, Guy Harris wrote:
2) it's easier to get them to open About - Wireshark than to figure
up whatever tool is appropriate on their particular OS or to
otherwise
get the CPU information.
right, but why build that into wireshark with all hassles of
interoperability?
-Original Message-
From: wireshark-dev-boun...@wireshark.org
[mailto:wireshark-dev-boun...@wireshark.org] On Behalf Of Kurt Knochner
Sent: den 7 februari 2013 16:59
To: wireshark-dev@wireshark.org
Subject: Re: [Wireshark-dev] Get_cpu_info on platforms other than Windows?
On 2013-02-06
Hi,
The included patch works on Ubuntu 64 bits but I guess it needs to be protected
with more #if defined on say OSX ppc?
Suggestions?
Regards
Anders
version_info.c.diff
Description: version_info.c.diff
___
Sent via:
On 06.02.2013 05:13, Anders Broman wrote:
Hi,
The included patch works on Ubuntu 64 bits but I guess it needs to be protected
with more #if defined on say OSX ppc?
#if defined(__i386__) || defined(__x86_64__)
#if defined(_MSC_VER)
// your windows version, compiled by a Microsoft compiler
#elif
On Feb 6, 2013, at 5:13 AM, Anders Broman anders.bro...@ericsson.com wrote:
The included patch works on Ubuntu 64 bits but I guess it needs to be
protected with more #if defined on say OSX ppc?
Well, obviously, for PPC *and* all other non-x86 CPUs:
http://www.debian.org/ports/
On Feb 6, 2013, at 12:13 PM, Guy Harris g...@alum.mit.edu wrote:
Note also that the CPUID instruction first showed up on the 486; Wireshark
might not run very well on a 386 box, but we should at least arrange not to
crash with an illegal instruction fault.
And here's Intel's documentation
Why do we need to show system information in Wireshark which is
available in system specific tools which are better suited for this
task?
Cheers,
Balint
2013/2/6 Anders Broman anders.bro...@ericsson.com:
Hi,
The included patch works on Ubuntu 64 bits but I guess it needs to be
protected with
On Feb 6, 2013, at 1:05 PM, Bálint Réczey bal...@balintreczey.hu wrote:
Why do we need to show system information in Wireshark which is
available in system specific tools which are better suited for this
task?
It *might* be interesting for performance questions if
1) the user
On Feb 6, 2013, at 12:13 PM, Guy Harris g...@alum.mit.edu wrote:
Whether an asm would work would depend more on the compiler than on the OS;
...but, then again, maybe the OS has already done all the heavy lifting for you:
$ uname -sr
Darwin 12.2.1
$ sysctl
Guy Harris skrev 2013-02-06 22:52:
On Feb 6, 2013, at 1:05 PM, Bálint Réczey bal...@balintreczey.hu wrote:
Why do we need to show system information in Wireshark which is
available in system specific tools which are better suited for this
task?
It *might* be interesting for performance
10 matches
Mail list logo
