-
m-relay
<fiatdemise:matrix.org> Hello, in GUI wallet, when restoring from mnemonic seed, the description says "Enter your private keys or 25 word mnemonic seed to restore your wallet"
-
m-relay
<fiatdemise:matrix.org> What if you have a Polyseed wallet?
-
m-relay
<fiatdemise:matrix.org> (that has 16 words)
-
plowsof
Currently not supported in monero gui/core
-
m-relay
<fiatdemise:matrix.org> OK, thx
-
plowsof
Iirc you can convert a 25 word seed to polyseed. But not the other way. This is possible in #feather-wallet but please confirm
-
m-relay
<ofrnxmr:agoradesk.com> Otherway
-
m-relay
<ofrnxmr:agoradesk.com> You can convert 16 > 25, but not 25 > 16
-
m-relay
<ofrnxmr:agoradesk.com> Its possible in cake too. If you restore 16 word, it shows the 25 word on the seed/backup page
-
sech1
selsta I tried to reproduce that crash on my notebook and now it really crashes (Windows 10 22H2). So now I can at least start debugging it
-
sech1
It didn't crash before 22H2 update
-
m-relay
<rbrunner7:monero.social> sech1, just curious, can you do proper debugging on Windows with Monero and other C++ based code? If yes, what tool(s) do you use?
-
sech1
That's what I will try today
-
sech1
building debug-static-win64 build now
-
m-relay
<rbrunner7:monero.social> Ok. Please report back :)
-
sech1
Either gdb in msys2 or Visual Studio debugger should work
-
sech1
lol, it doesn't even build - some linker errors
-
plowsof
-
plowsof
from elibroftw
-
m-relay
<rbrunner7:monero.social> From the blog entry: "an unsupported debug-static-win64 build target" Yeah ...
-
sech1
yes, that one didn't build
-
sech1
Although I'm getting linker errors even with release-static-win64, maybe my msys2 setup is broken
-
sech1
or maybe no one checked if it builds at all
-
sech1
uhhh, monerod that I built locally doesn't crash. I'll keep investigating.
-
sech1
Either it's an undefined behavior somewhere and different compilers produce different results, or it's a compiler bug in the version that was used to build release binaries
-
plowsof
Release binaries are from gitisn selsta?
-
plowsof
gitian*
-
selsta
yes gitian
-
plowsof
maybe guix binaries "fix it"
-
plowsof
I cant access the guix binaries until evening if sech1 wants to test
monero-project/monero #8929#issuecomment-1971599972
-
m-relay
-
m-relay
<tobtoht:monero.social> note this is based on master, not release-v0.18
-
plowsof
Thanks tobtoht
-
sech1
I can't make that build crash
-
sech1
Monero 'Fluorine Fermi' (v0.18.1.0-80e152548)
-
sech1
the 0.18.3.1-release crashes pretty quickly
-
sech1
It crashes randomly after "start_mining ..." command, sometimes I need to repeat start-stop a few times, but it crashes
-
sech1
the build from bootstrappable PR doesn't crash
-
m-relay
<tobtoht:monero.social> they're built with gcc 10.5.0. gitian uses 7.3.0 iirc
-
m-relay
<tobtoht:monero.social> version is stuck at v0.18.1.0 on master
-
sech1
I know, I double checked it uses the recent commit (80e152548)
-
m-relay
<tobtoht:monero.social> i mean the version string is just wrong
-
m-relay
<tobtoht:monero.social> ah ok
-
sech1
so both miner.cpp and rx-slow-hash.c have the latest code there
-
sech1
which mean 7.3.0 compiles the code differently
-
sech1
option 1 is undefined behavior somewhere, option 2 is 7.3.0 has a bug
-
m-relay
<tobtoht:monero.social> problem is we can't easily bump it in gitian (whereas this is trivial in guix)
-
selsta
can we disable all optimizations in gitian build?
-
m-relay
<tobtoht:monero.social> yea
-
sech1
my local build used gcc 13.2.0 - that one didn't crash as well
-
sech1
I compiled monero with -fsanitize-undefined but it didn't find anything in the mining code, so I guess it's gcc 7.3.0 issue
-
sech1
monerod with -fsanitize=undefined
-
sech1
it found a few other issues though
-
m-relay
-
sech1
/usr/bin/i686-w64-mingw32-as: CMakeFiles/obj_wallet.dir/wallet2.cpp.obj: too many sections (44259)
-
sech1
/tmp/ccYdijd6.s: Fatal error: can't write 157 bytes to section .text of CMakeFiles/obj_wallet.dir/wallet2.cpp.obj: 'File too big'
-
sech1
wow
-
moneromoooo
Known windows shitness, from antediluvian linker compat. You might get past that if you use -mbig-obj (IIRC). If it's already there, don't use Windows :)
-
sech1
But it uses Ubuntu to build
-
sech1
or is it the problem with *.obj file format?
-
moneromoooo
Yes, file format, 32k/64k limit of something.
-
moneromoooo
Hence antediluvian linker compat.
-
sech1
why is it hard to bump gcc version in gitian?
-
m-relay
<tobtoht:monero.social> we are stuck with ubuntu 20.04 packages
-
m-relay
<tobtoht:monero.social> 18.04*
-
m-relay
<tobtoht:monero.social> bumping ubuntu would bump mininum glibc
-
m-relay
<tobtoht:monero.social> oh, it's defined per platform. so we could bump for windows only
-
sech1
Can't we install gcc 10 on 18.04? sudo add-apt-repository ppa:ubuntu-toolchain-r/test & sudo apt-get update & sudo apt install gcc-10
-
sech1
or even gcc 11
-
m-relay
<tobtoht:monero.social> need cross-compilation toolchain g++-mingw-64
-
m-relay
<tobtoht:monero.social> also I would advise against trusting binaries from PPAs
-
sech1
if we bump to 20.04 for windows, it should work just fine. There's no glibc version incompatibilites there
-
m-relay
<tobtoht:monero.social> yes, going to try that
-
m-relay
<tobtoht:monero.social> nice timing
githubstatus.com
-
m-relay
<tobtoht:monero.social> sech1: here is a build with 20.04:
github.com/tobtoht/monero/actions/runs/8113997670
-
sech1
testing now
-
sech1
crashes
-
m-relay
<tobtoht:monero.social> nice
-
m-relay
<tobtoht:monero.social> let me double check the build
-
sech1
20.04 has gcc 9 by default?
-
sech1
it probably needs gcc 10 or 11 to work properly
-
sech1
I mean it crashes when I try to run start_mining
-
m-relay
<tobtoht:monero.social> "20.04 has gcc 9 by default?" <- 9.3.0 yea
-
m-relay
<tobtoht:monero.social> i can try 22.04
-
m-relay
<tobtoht:monero.social> might mess up reproducibility, packages don't appear to be pinned and 22.04 is still getting updates
-
m-relay
<tobtoht:monero.social> sech1: 22.04, gcc 11.4.0:
github.com/tobtoht/monero/actions/runs/8114828674
-
sech1
hmm, it still crashes
-
m-relay
<tobtoht:monero.social> ok i'm not sure what the deal is then
-
sech1
My local build didn't crash, but it was gcc 13.2.0
-
sech1
And I built it in msys2
-
sech1
guix build doesn't crash too
-
m-relay
<tobtoht:monero.social> try this 20.04 -O1 for good measure:
github.com/tobtoht/monero/actions/runs/8112990839
-
m-relay
<tobtoht:monero.social> 18.04*
-
m-relay
<tobtoht:monero.social> keep confusing these
-
sech1
-
sech1
-
m-relay
<tobtoht:monero.social> not sure how viable backporting #8929 to the release branch is
-
m-relay
<tobtoht:monero.social> needs to be reviewed first, anyway
-
sech1
so far, gcc 10.5.0 and gcc 13.2.0 seem to build a working binary
-
m-relay
<tobtoht:monero.social> just to be sure, release-v0.18 isn't known to have other issues?
-
m-relay
<tobtoht:monero.social> 20.04 / 22.04 builds were based on release
-
sech1
They shouldn't
-
sech1
Mining works in Windows 10 21H2 and doesn't work in Windows 10 22H2 and in Windows 11
-
sech1
so when 0.18.3.1 released, everything worked for everyone, but then Windows updated and it stopped working
-
sech1
also, it's not a gui issue, it's a crash in monerod
-
sech1
All I know is I can't reproduce it with local build (gcc 13.2.0), and the release build doesn't show a good callstack. It crashes when calling ReleaseSRWLockShared (resource not owned exception), but I checked all places where this function is called and they all seem fine
-
sech1
So I suspect some compiler bug
-
m-relay
<tobtoht:monero.social> i'm pretty sure the problem is mingw-w64. 22.04 uses 8.0.0, a version from 2020
-
m-relay
<tobtoht:monero.social> guix builds use 11.0.1 and msys2 is rolling release