Github messages for voidlinux
 help / color / mirror / Atom feed
From: devlocalhost <devlocalhost@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: mega-cmd cannot login due to mega-cmd-server crashing
Date: Sat, 10 Feb 2024 23:38:08 +0100	[thread overview]
Message-ID: <20240210223808.944E324572@inbox.vuxu.org> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-48644@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 3458 bytes --]

New comment by devlocalhost on void-packages repository

https://github.com/void-linux/void-packages/issues/48644#issuecomment-1937309877

Comment:
here's what gdb says:
```
(gdb) bt
#0  __memcpy_ssse3 () at ../sysdeps/x86_64/multiarch/memmove-ssse3.S:67
#1  0x00007ffff77882b3 in std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >::_M_append(char const*, unsigned long) () from /usr/lib/libstdc++.so.6
#2  0x00007ffff7bdedfb in mega::Node::serialize (this=0x7fffb416b1a0, d=0x7ffff37ff070)
    at src/node.cpp:558
#3  0x00007ffff7bc32b9 in mega::DbTable::put (this=0x7fffb40206a0, type=type@entry=1,
    record=0x7fffb416b1a0, key=key@entry=0x5555556d6d68) at src/db.cpp:44
#4  0x00007ffff7b3b273 in mega::MegaClient::updatesc (this=this@entry=0x5555556d5c50)
    at src/megaclient.cpp:4880
#5  0x00007ffff7b60d4b in mega::MegaClient::notifypurge (this=this@entry=0x5555556d5c50)
    at src/megaclient.cpp:6767
#6  0x00007ffff7b671b0 in mega::MegaClient::exec (this=<optimized out>)
    at src/megaclient.cpp:2846
#7  0x00007ffff7cd25f9 in mega::MegaApiImpl::loop (this=0x5555556970a0)
    at src/megaapi_impl.cpp:6301
#8  0x00007ffff7cd26ad in mega::MegaApiImpl::threadEntryPoint (param=0x5555556970a0)
    at src/megaapi_impl.cpp:5038
#9  0x00007ffff728a36b in start_thread (arg=<optimized out>) at ./nptl/pthread_create.c:444
#10 0x00007ffff730c298 in clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:78
```

since i see "ssse3", heres lscpu output:
```
Architecture:           x86_64
  CPU op-mode(s):       32-bit, 64-bit
  Address sizes:        36 bits physical, 48 bits virtual
  Byte Order:           Little Endian
CPU(s):                 2
  On-line CPU(s) list:  0,1
Vendor ID:              GenuineIntel
  Model name:           Intel(R) Core(TM)2 Duo CPU     P7450  @ 2.13GHz
    CPU family:         6
    Model:              23
    Thread(s) per core: 1
    Core(s) per socket: 2
    Socket(s):          1
    Stepping:           6
    CPU(s) scaling MHz: 75%
    CPU max MHz:        2133.0000
    CPU min MHz:        800.0000
    BogoMIPS:           4256.45
    Flags:              fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse
                        36 clflush dts acpi mmx fxsr sse sse2 ht tm pbe syscall nx lm constan
                        t_tsc arch_perfmon pebs bts rep_good nopl cpuid aperfmperf pni dtes64
                         monitor ds_cpl est tm2 ssse3 cx16 xtpr pdcm sse4_1 lahf_lm dtherm
Caches (sum of all):
  L1d:                  64 KiB (2 instances)
  L1i:                  64 KiB (2 instances)
  L2:                   3 MiB (1 instance)
NUMA:
  NUMA node(s):         1
  NUMA node0 CPU(s):    0,1
Vulnerabilities:
  Gather data sampling: Not affected
  Itlb multihit:        KVM: Mitigation: VMX unsupported
  L1tf:                 Mitigation; PTE Inversion
  Mds:                  Vulnerable; SMT disabled
  Meltdown:             Vulnerable
  Mmio stale data:      Unknown: No mitigations
  Retbleed:             Not affected
  Spec rstack overflow: Not affected
  Spec store bypass:    Vulnerable
  Spectre v1:           Vulnerable: __user pointer sanitization and usercopy barriers only; n
                        o swapgs barriers
  Spectre v2:           Vulnerable, STIBP: disabled, PBRSB-eIBRS: Not affected
  Srbds:                Not affected
  Tsx async abort:      Not affected
```

      parent reply	other threads:[~2024-02-10 22:38 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-10 22:36 [ISSUE] " devlocalhost
2024-02-10 22:36 ` devlocalhost
2024-02-10 22:38 ` devlocalhost [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20240210223808.944E324572@inbox.vuxu.org \
    --to=devlocalhost@users.noreply.github.com \
    --cc=ml@inbox.vuxu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).