04:50:47 <m-relay> <f​iatdemise: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"
04:51:03 <m-relay> <f​iatdemise:matrix.org> What if you have a Polyseed wallet?
04:53:30 <m-relay> <f​iatdemise:matrix.org> (that has 16 words)
04:54:41 <plowsof> Currently not supported in monero gui/core
05:05:26 <m-relay> <f​iatdemise:matrix.org> OK, thx
05:06:53 <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 
06:06:02 <m-relay> <o​frnxmr:agoradesk.com> Otherway
06:06:04 <m-relay> <o​frnxmr:agoradesk.com> You can convert 16 > 25, but not 25 > 16
06:06:31 <m-relay> <o​frnxmr:agoradesk.com> Its possible in cake too. If you restore 16 word, it shows the 25 word on the seed/backup page
08:42:43 <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
08:44:30 <sech1> It didn't crash before 22H2 update
09:02:30 <m-relay> <r​brunner7: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?
09:02:47 <sech1> That's what I will try today
09:02:56 <sech1> building debug-static-win64 build now
09:03:08 <m-relay> <r​brunner7:monero.social> Ok. Please report back :)
09:03:16 <sech1> Either gdb in msys2 or Visual Studio debugger should work
09:03:50 <sech1> lol, it doesn't even build - some linker errors
09:48:11 <plowsof> sech1 anything useful here? https://blog.elijahlopez.ca/posts/monero-devs-windows/
09:48:28 <plowsof> from elibroftw
09:54:28 <m-relay> <r​brunner7:monero.social> From the blog entry: "an unsupported debug-static-win64 build target" Yeah ...
09:56:49 <sech1> yes, that one didn't build
09:57:11 <sech1> Although I'm getting linker errors even with release-static-win64, maybe my msys2 setup is broken
09:57:27 <sech1> or maybe no one checked if it builds at all
10:52:02 <sech1> uhhh, monerod that I built locally doesn't crash. I'll keep investigating.
11:05:40 <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
12:24:11 <plowsof> Release binaries are from gitisn selsta?
12:24:19 <plowsof> gitian*
12:24:51 <selsta> yes gitian
12:25:23 <plowsof> maybe guix binaries "fix it" 
12:32:17 <plowsof> I cant access the guix binaries until evening if sech1 wants to test https://github.com/monero-project/monero/pull/8929#issuecomment-1971599972
12:37:19 <m-relay> <t​obtoht:monero.social> they're available on ci: https://github.com/monero-project/monero/actions/runs/8047961641
12:37:40 <m-relay> <t​obtoht:monero.social> note this is based on master, not release-v0.18
12:44:52 <plowsof> Thanks tobtoht
12:56:07 <sech1> I can't make that build crash
12:56:22 <sech1> Monero 'Fluorine Fermi' (v0.18.1.0-80e152548)
12:56:31 <sech1> the 0.18.3.1-release crashes pretty quickly
12:58:26 <sech1> It crashes randomly after "start_mining ..." command, sometimes I need to repeat start-stop a few times, but it crashes
12:58:47 <sech1> the build from bootstrappable PR doesn't crash
13:02:08 <m-relay> <t​obtoht:monero.social> they're built with gcc 10.5.0. gitian uses 7.3.0 iirc
13:02:15 <m-relay> <t​obtoht:monero.social> version is stuck at v0.18.1.0 on master
13:02:33 <sech1> I know, I double checked it uses the recent commit (80e152548)
13:02:34 <m-relay> <t​obtoht:monero.social> i mean the version string is just wrong
13:02:39 <m-relay> <t​obtoht:monero.social> ah ok
13:02:55 <sech1> so both miner.cpp and rx-slow-hash.c have the latest code there
13:03:06 <sech1> which mean 7.3.0 compiles the code differently
13:03:20 <sech1> option 1 is undefined behavior somewhere, option 2 is 7.3.0 has a bug
13:27:27 <m-relay> <t​obtoht:monero.social> problem is we can't easily bump it in gitian (whereas this is trivial in guix)
13:45:41 <selsta> can we disable all optimizations in gitian build?
13:46:20 <m-relay> <t​obtoht:monero.social> yea
13:46:52 <sech1> my local build used gcc 13.2.0 - that one didn't crash as well
14:09:33 <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
14:09:53 <sech1> monerod with -fsanitize=undefined
14:09:58 <sech1> it found a few other issues though
14:38:25 <m-relay> <t​obtoht:monero.social> -O0 build fails.. https://github.com/tobtoht/monero/actions/runs/8112553952/job/22174033692#step:4:33626
15:00:08 <sech1>  /usr/bin/i686-w64-mingw32-as: CMakeFiles/obj_wallet.dir/wallet2.cpp.obj: too many sections (44259)
15:00:10 <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'
15:00:12 <sech1> wow
15:02:52 <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 :)
15:06:16 <sech1> But it uses Ubuntu to build
15:07:13 <sech1> or is it the problem with *.obj file format?
15:09:53 <moneromoooo> Yes, file format, 32k/64k limit of something.
15:10:03 <moneromoooo> Hence antediluvian linker compat.
15:13:35 <sech1> why is it hard to bump gcc version in gitian?
15:14:02 <m-relay> <t​obtoht:monero.social> we are stuck with ubuntu 20.04 packages
15:14:23 <m-relay> <t​obtoht:monero.social> 18.04*
15:14:51 <m-relay> <t​obtoht:monero.social> bumping ubuntu would bump mininum glibc
15:17:53 <m-relay> <t​obtoht:monero.social> oh, it's defined per platform. so we could bump for windows only
15:18:39 <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
15:18:49 <sech1> or even gcc 11
15:19:10 <m-relay> <t​obtoht:monero.social> need cross-compilation toolchain g++-mingw-64
15:20:29 <m-relay> <t​obtoht:monero.social> also I would advise against trusting binaries from PPAs
15:20:31 <sech1> if we bump to 20.04 for windows, it should work just fine. There's no glibc version incompatibilites there
15:20:43 <m-relay> <t​obtoht:monero.social> yes, going to try that
15:28:12 <m-relay> <t​obtoht:monero.social> nice timing https://www.githubstatus.com/
17:03:04 <m-relay> <t​obtoht:monero.social> sech1: here is a build with 20.04: https://github.com/tobtoht/monero/actions/runs/8113997670
17:06:21 <sech1> testing now
17:06:34 <sech1> crashes
17:06:39 <m-relay> <t​obtoht:monero.social> nice
17:06:52 <m-relay> <t​obtoht:monero.social> let me double check the build
17:06:57 <sech1> 20.04 has gcc 9 by default?
17:07:05 <sech1> it probably needs gcc 10 or 11 to work properly
17:07:20 <sech1> I mean it crashes when I try to run start_mining
17:09:30 <m-relay> <t​obtoht:monero.social> "20.04 has gcc 9 by default?" <- 9.3.0 yea
17:10:38 <m-relay> <t​obtoht:monero.social> i can try 22.04
17:20:55 <m-relay> <t​obtoht:monero.social> might mess up reproducibility, packages don't appear to be pinned and 22.04 is still getting updates
18:09:05 <m-relay> <t​obtoht:monero.social> sech1: 22.04, gcc 11.4.0: https://github.com/tobtoht/monero/actions/runs/8114828674
18:12:02 <sech1> hmm, it still crashes
18:12:17 <m-relay> <t​obtoht:monero.social> ok i'm not sure what the deal is then
18:12:32 <sech1> My local build didn't crash, but it was gcc 13.2.0
18:12:44 <sech1> And I built it in msys2
18:12:51 <sech1> guix build doesn't crash too
18:13:06 <m-relay> <t​obtoht:monero.social> try this 20.04 -O1 for good measure: https://github.com/tobtoht/monero/actions/runs/8112990839
18:13:11 <m-relay> <t​obtoht:monero.social> 18.04*
18:13:18 <m-relay> <t​obtoht:monero.social> keep confusing these
18:13:20 <sech1> this one doesn't crash: https://github.com/monero-project/monero/actions/runs/8047961641
18:14:39 <sech1> https://github.com/tobtoht/monero/actions/runs/8112990839 crashes
18:15:00 <m-relay> <t​obtoht:monero.social> not sure how viable backporting #8929 to the release branch is
18:15:03 <m-relay> <t​obtoht:monero.social> needs to be reviewed first, anyway
18:18:11 <sech1> so far, gcc 10.5.0 and gcc 13.2.0 seem to build a working binary
18:20:54 <m-relay> <t​obtoht:monero.social> just to be sure, release-v0.18 isn't known to have other issues?
18:21:15 <m-relay> <t​obtoht:monero.social> 20.04 / 22.04 builds were based on release
18:22:20 <sech1> They shouldn't
18:22:37 <sech1> Mining works in Windows 10 21H2 and doesn't work in Windows 10 22H2 and in Windows 11
18:24:24 <sech1> so when 0.18.3.1 released, everything worked for everyone, but then Windows updated and it stopped working
18:24:45 <sech1> also, it's not a gui issue, it's a crash in monerod
18:26:03 <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
18:26:08 <sech1> So I suspect some compiler bug
18:55:46 <m-relay> <t​obtoht:monero.social> i'm pretty sure the problem is mingw-w64. 22.04 uses 8.0.0, a version from 2020
18:55:53 <m-relay> <t​obtoht:monero.social> guix builds use 11.0.1 and msys2 is rolling release