Client Crashes with sendtoaddress

[nharmon9]

After updating elementsd on regtest crashes when trying to sendtoaddress.

Log spits out:

2019-11-16T00:47:30Z Received a POST request for / from 127.0.0.1:50217
2019-11-16T00:47:30Z ThreadRPCServer method=getnewaddress user=user2
2019-11-16T00:47:30Z [default wallet] keypool reserve 3
2019-11-16T00:47:30Z [default wallet] keypool keep 3
2019-11-16T00:47:30Z Received a POST request for / from 127.0.0.1:50218
2019-11-16T00:47:30Z ThreadRPCServer method=sendtoaddress user=user2
2019-11-16T00:47:30Z [default wallet] keypool added 1 keys (0 internal), size=2000 (1000 internal)
2019-11-16T00:47:30Z [default wallet] keypool reserve 1001
2019-11-16T00:47:30Z [default wallet] Unblinding single blinded output at index 0 due to lack of inputs and other outputs being blinded.

Then in the terminal:

error: Could not connect to the server 127.0.0.1:18885 (error code 1 - "EOF reached")

This happens every time when doing the tutorial.

Bitcoin Core Version: 0.18.99.0

MacOSX 10.15.1

[instagibbs]

Is there any way you can get a backtrace on it? I'll take a look at it soon to see if I can notice something obvious around that log line.

…

On Fri, Nov 15, 2019, 7:57 PM nharmon9 ***@***.***> wrote: After updating elementsd on regtest crashes when trying to sendtoaddress. Log spits out: 2019-11-16T00:47:30Z Received a POST request for / from 127.0.0.1:50217 2019-11-16T00:47:30Z ThreadRPCServer method=getnewaddress user=user2 2019-11-16T00:47:30Z [default wallet] keypool reserve 3 2019-11-16T00:47:30Z [default wallet] keypool keep 3 2019-11-16T00:47:30Z Received a POST request for / from 127.0.0.1:50218 2019-11-16T00:47:30Z ThreadRPCServer method=sendtoaddress user=user2 2019-11-16T00:47:30Z [default wallet] keypool added 1 keys (0 internal), size=2000 (1000 internal) 2019-11-16T00:47:30Z [default wallet] keypool reserve 1001 2019-11-16T00:47:30Z [default wallet] Unblinding single blinded output at index 0 due to lack of inputs and other outputs being blinded. Then in the terminal: error: Could not connect to the server 127.0.0.1:18885 (error code 1 - "EOF reached") This happens every time when doing the tutorial. Bitcoin Core Version: 0.18.99.0 MacOSX 10.15.1 — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#782?email_source=notifications&email_token=ABMAFU3A5MBIMRUX5TD6VVTQT5AQ7A5CNFSM4JOCVVLKYY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4HZYAH6Q>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABMAFU27UWNIFKP6NTQOEKLQT5AQ7ANCNFSM4JOCVVLA> .

[nharmon9]

Sure. How does one do that?

[instagibbs]

Not sure how to do on Mac to be honest. I'll come back to you.

…

On Fri, Nov 15, 2019, 8:04 PM nharmon9 ***@***.***> wrote: Sure. How does one do that? — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#782?email_source=notifications&email_token=ABMAFUYUN3EC7YYB2CSTHS3QT5BKNA5CNFSM4JOCVVLKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEEHFFLQ#issuecomment-554586798>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABMAFU2JJFXGV7ZE273YFT3QT5BKNANCNFSM4JOCVVLA> .

[instagibbs]

Oh. Are you actually doing "-regtest"? Try chain=elementsregtest or something similar. Regtest is actually bitcoins regtest which doesn't have blinding.

…

On Fri, Nov 15, 2019, 8:08 PM Greg Sanders ***@***.***> wrote: Not sure how to do on Mac to be honest. I'll come back to you. On Fri, Nov 15, 2019, 8:04 PM nharmon9 ***@***.***> wrote: > Sure. How does one do that? > > — > You are receiving this because you commented. > Reply to this email directly, view it on GitHub > <#782?email_source=notifications&email_token=ABMAFUYUN3EC7YYB2CSTHS3QT5BKNA5CNFSM4JOCVVLKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEEHFFLQ#issuecomment-554586798>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/ABMAFU2JJFXGV7ZE273YFT3QT5BKNANCNFSM4JOCVVLA> > . >

[nharmon9]

I have chain=elementsregtest. I was building something with elements and it started acting strange so I wiped it and went back to the tutorial and this was the result.

[instagibbs]

Try running the elements daemon using gdb or lldb, depending on what's installed on your machine: https://stackoverflow.com/questions/41966073/how-to-install-gdb-on-macos-terminal-sierra

if you can run it there, then once it crashes you should be able to coax it into giving a stack trace.

f.e.,

gdb --args elemensd <your arguments here for chainparams or datadirs
r for run
bt for backtrace

[instagibbs]

lldb – bitcoind <args> should be the equivalent for mac by default, with bt to get the backtrace

[instagibbs]

this has been reported by another Mac user running functional tests... investigating

[instagibbs]

Looks like I've found the issue and maybe fixed: #787

[philippem]

This can be reproduced by running the Elements functional test feature_dynafed.py on macOs Catalina (elements master fe27ef)

A screenshot of the crash follows:

[instagibbs]

update: i have not found the issue, closed 787

[stevenroose]

@philippem That screenshot confuses me. Your breakpoints are in BlindTransaction (IIRC), but the stacktrace on the left suggests you're in CWallet::CreateTransaction. Any chance you can find the exact line that's making it panic?

[instagibbs]

@stevenroose it it crashing as soon as it enters BlindTransaction

[instagibbs]

Ok we have 2 reports of Catalina crashes, and two negative report from High Sierra 10.13.6

[gwillen]

Also passes on 10.13.6 for me unfortunately, and I don't have access to a machine with Catalina.