Wireshark, running on -current, is dumping core ('illegal instruction') on
two separate pentium ii systems here. It's fine on a Core2Duo running i386.
I'm presuming it's using pentium 3 or later instructions/SSE2 etc. Has
anyone else seen this before I look at it?
PK
Peter Kay wrote:
> Wireshark, running on -current, is dumping core ('illegal
> instruction') on two separate pentium ii systems here. It's fine on a
> Core2Duo running i386.
>
> I'm presuming it's using pentium 3 or later instructions/SSE2 etc. Has
> anyone else seen this before I look at it?
Can
It's a MOVSD SSE instruction. Tshark is ok. I can cope with that or tcpdump
if need be, but here's the output :
Starting program: /usr/local/bin/wireshark
warning: Lowest section in /usr/local/lib/libicudata.so.9.0 is .hash at
0154
Program received signal SIGILL, Illegal instruction.
0x06d685
On 2016-03-15, Peter Kay wrote:
> It's a MOVSD SSE instruction. Tshark is ok. I can cope with that or tcpdump
> if need be, but here's the output :
I think this variant of MOVSD might be AVX?
> Starting program: /usr/local/bin/wireshark
> warning: Lowest section in /usr/local/lib/libicudata.so.9
On Tue, Mar 15, 2016 at 06:33:56PM +, Stuart Henderson wrote:
> On 2016-03-15, Peter Kay wrote:
> > It's a MOVSD SSE instruction. Tshark is ok. I can cope with that or tcpdump
> > if need be, but here's the output :
>
> I think this variant of MOVSD might be AVX?
>
> > Starting program: /usr
On 2016-03-15, Stuart Henderson wrote:
> Looks like Qt autodetects at build time, we probably want to configure
> on i386 with no-avx, no-avx2, no-sse4.1, no-sse4.2, maybe no-ssse3.
> (SSE2 is probably reasonable to expect for Qt5 apps, it's present on
> Netburst, Pentium-M, Atom, C7 etc. which s
Not wishing to be a dick about this, but what sort of notification is
in place to stop time being wasted trying to run programs on
incompatible CPUs? Obviously old processors need to be supported in
base for embedded systems, but it would be nice to have a note for
packages.
Is it viable to redire
It's not an AVX instruction, as Wireshark runs on a Core2Duo pre Sandy
Bridge when AVX arrived.
I agree that it looks too heavy for a P2, and last time I ran it under
*nix it would have been the gtk version, I was surprised at all the
dependencies it pulled in.
This issue is only likely to get wo
2016-03-15 21:33 GMT+03:00 Stuart Henderson :
> On 2016-03-15, Peter Kay wrote:
>> It's a MOVSD SSE instruction. Tshark is ok. I can cope with that or tcpdump
>> if need be, but here's the output :
>
> I think this variant of MOVSD might be AVX?
>
>> Starting program: /usr/local/bin/wireshark
>> w
On 2016/03/16 13:42, Peter Kay wrote:
> It's not an AVX instruction, as Wireshark runs on a Core2Duo pre Sandy
> Bridge when AVX arrived.
>
> I agree that it looks too heavy for a P2, and last time I ran it under
> *nix it would have been the gtk version, I was surprised at all the
> dependencies
Peter Kay:
> Not wishing to be a dick about this, but what sort of notification is
> in place to stop time being wasted trying to run programs on
> incompatible CPUs?
None. The general policy is that packages must run on all CPUs
supported by the base system.
That said, we now do have a few port
11 matches
Mail list logo
