From: "Martinx - ジェームズ" <thiagocmartinsc@gmail.com>
To: Gavin Andresen <gavinandresen@gmail.com>
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Need help testing/debugging: Linux64
Date: Mon, 21 Nov 2011 14:28:03 -0200 [thread overview]
Message-ID: <CAJSM8J3Pmht+8qoHgZTa6u=CnZKLeH1aBy31nfAoLdAHPXrZQw@mail.gmail.com> (raw)
In-Reply-To: <CABsx9T2KkFC9_sibE4gYdd2JCTSSdbVQcOmK1nbKFYns820_7A@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1436 bytes --]
Gavin,
I try to reproduce the error by doing this (Ubuntu 11.10 64bits):
rm -rf ~/bitcoin # CAUTION
./bitcoin-0.4.0-linux/bin/64/bitcoin
* Encrypt my wallet
* Close Bitcoin 0.4.0
Next open Bitcoin 0.5.0rc7:
./bitcoin-0.5.0rc7-linux/bin/64/bitcoin-qt
* Automatic wallet upgrade (I guess) working... No crashs...
Best,
Thiago
On 19 November 2011 14:20, Gavin Andresen <gavinandresen@gmail.com> wrote:
> There is one issue holding up a 0.5.0/0.4.1 final release: I've seen
> a couple of bug reports of crashes on startup when re-encrypting
> previously encrypted wallets on Linux64 systems.
>
> I've tried to reproduce on Ubuntu 10.10 server and "it worked for me"
> -- so I need help figuring out what is going on (is it only bitcoin-qt
> that is crashing? Is Ubuntu OK but other linux variations broken?
> etc)
>
> --
> --
> Gavin Andresen
>
>
> ------------------------------------------------------------------------------
> All the data continuously generated in your IT infrastructure
> contains a definitive record of customers, application performance,
> security threats, fraudulent activity, and more. Splunk takes this
> data and makes sense of it. IT sense. And common sense.
> http://p.sf.net/sfu/splunk-novd2d
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>
[-- Attachment #2: Type: text/html, Size: 2182 bytes --]
prev parent reply other threads:[~2011-11-21 16:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-19 16:20 [Bitcoin-development] Need help testing/debugging: Linux64 Gavin Andresen
2011-11-21 16:28 ` Martinx - ジェームズ [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='CAJSM8J3Pmht+8qoHgZTa6u=CnZKLeH1aBy31nfAoLdAHPXrZQw@mail.gmail.com' \
--to=thiagocmartinsc@gmail.com \
--cc=bitcoin-development@lists.sourceforge.net \
--cc=gavinandresen@gmail.com \
/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