[Guide] How to create your customized Bitcoin-Address (vanitygen) – step by step

[DYING_S0UL]

it worked like a charm!

It's not supposed to end in a segfault.

It was my first time using it, so I'm not familiar with the errors and stuff. Will you kindly tell me what went wrong or the cause of this? 

[LoyceV]

Will you kindly tell me what went wrong or the cause of this? 

I can't tell you that. It's supposed to end gracefully, not in a segfault. What happens if you set it to continue searching after it finds a match?

[DYING_S0UL]

I can't tell you that. It's supposed to end gracefully, not in a segfault. What happens if you set it to continue searching after it finds a match?

When I set it to continue searching, it searches infinitely, after finding a match! And when I set a certain limit, like 10 addresses, it stops after finding 10 addresses. But this time no segmentation fault was seen.

[nc50lc]

Here is what I was able to generate:

That is 10gic's Vanitygen-plusplus right?
Tip for that fork: For real-world usage, use -F compressed for it to generate compressed WIF private key format,
the uncompressed form (although valid) is already deprecated and will produce quite higher transaction input size than the former.

Example:

Code:

./oclvanitygen++ -F compressed 1BANANA
Difficulty: 15058417127
create thread!
Pattern: 1BANANA
Address: 1BANANAdrKtLW6kvPWgt2BBrGXAj6QzpGA
Privkey: KyE8ScdDezEHg87KX7kJgMRqEhqgtAPFxW6zM3zskxMxopQpwubT

It's not supposed to end in a segfault.

It was my first time using it, so I'm not familiar with the errors and stuff. Will you kindly tell me what went wrong or the cause of this?  

"SegFault" is so generic that you'll never know the cause without looking at logs, code and OS to pinpoint the cause.
It's better to report it to its GitHub repository as a new issue.

[DYING_S0UL]

That is 10gic's Vanitygen-plusplus right?
Tip for that fork: For real-world usage, use -F compressed for it to generate compressed WIF private key format,
the uncompressed form (although valid) is already deprecated and will produce quite higher transaction input size than the former.

Yes, it's 10gic's forked version, since the original repo isn't maintained anymore, i used this instead. Thanks for the tip, I'll remember to use it when I run vanitygen++ again  . I am still exploring new options.....

SegFault" is so generic that you'll never know the cause without looking at logs, code and OS to pinpoint the cause.
It's better to report it to its GitHub repository as a new issue.

I googled it a bit to understand what this error was. Looks like it's  related to the OS not the program, not sure! Anyway, I'll report it, when i get the time.