Discussion:
[urbit] Arch urbit creation core dump
Matthew Piziak
2015-11-07 18:16:05 UTC
Permalink
I have an Arch droplet running on DigitalOcean with 1GB RAM and a 2GB swap
file.

When I run urbit -c mycomet , I get the following output:

~
urbit: home is mycomet
loom: mapped 2048MB
boot: installed 229 jets
boot: loading /home/matt/aur/urbit-git/src/urbit/urb/urbit.pill
arvo: time: ~2015.11.7..18.08.29..6daf

bail: oops
Aborted (core dumped)

Is there something else I need to do in order to create an urbit?

Thank you very much.
--
You received this message because you are subscribed to the Google Groups "urbit" group.
To unsubscribe from this group and stop receiving emails from it, send an email to urbit-dev+***@googlegroups.com.
To post to this group, send email to urbit-***@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Matthew Piziak
2015-11-07 18:21:54 UTC
Permalink
Now running urbit -c mycomet returns tried to create, but mycomet already
exists

Running urbit mycomet returns the same output as before:

~
urbit: home is mycomet
loom: mapped 2048MB
protected loom
live: logical boot
boot: installed 229 jets
boot: loading /home/matt/aur/urbit-git/src/urbit/urb/urbit.pill
arvo: time: ~2015.11.7..18.20.12..03f0

bail: oops
Aborted (core dumped)
Post by Matthew Piziak
I have an Arch droplet running on DigitalOcean with 1GB RAM and a 2GB swap
file.
~
urbit: home is mycomet
loom: mapped 2048MB
boot: installed 229 jets
boot: loading /home/matt/aur/urbit-git/src/urbit/urb/urbit.pill
arvo: time: ~2015.11.7..18.08.29..6daf
bail: oops
Aborted (core dumped)
Is there something else I need to do in order to create an urbit?
Thank you very much.
--
You received this message because you are subscribed to the Google Groups "urbit" group.
To unsubscribe from this group and stop receiving emails from it, send an email to urbit-dev+***@googlegroups.com.
To post to this group, send email to urbit-***@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Curtis Yarvin
2015-11-07 18:36:34 UTC
Permalink
That's extremely peculiar to say the least! I think we run fine in Arch. Or I thought so.

What would help is a stack trace. You can get a good trace by setting DEBUG=yes in the Makefile, then running gdb or lldb on the core.

Sent from my iPhone
Now running urbit -c mycomet returns tried to create, but mycomet already exists
~
urbit: home is mycomet
loom: mapped 2048MB
protected loom
live: logical boot
boot: installed 229 jets
boot: loading /home/matt/aur/urbit-git/src/urbit/urb/urbit.pill
arvo: time: ~2015.11.7..18.20.12..03f0
bail: oops
Aborted (core dumped)
I have an Arch droplet running on DigitalOcean with 1GB RAM and a 2GB swap file.
~
urbit: home is mycomet
loom: mapped 2048MB
boot: installed 229 jets
boot: loading /home/matt/aur/urbit-git/src/urbit/urb/urbit.pill
arvo: time: ~2015.11.7..18.08.29..6daf
bail: oops
Aborted (core dumped)
Is there something else I need to do in order to create an urbit?
Thank you very much.
--
You received this message because you are subscribed to the Google Groups "urbit" group.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups "urbit" group.
To unsubscribe from this group and stop receiving emails from it, send an email to urbit-dev+***@googlegroups.com.
To post to this group, send email to urbit-***@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Matthew Piziak
2015-11-07 18:53:25 UTC
Permalink
Thank you for the fast response. Here is the stack trace I get from gdb:

Starting program: /home/matt/aur/urbit-git/src/urbit/bin/urbit -c mycomet
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/usr/lib/libthread_db.so.1".
~
urbit: home is mycomet
loom: mapped 2048MB

Program received signal SIGSEGV, Segmentation fault.
0x00007ffff5df6af4 in __memset_sse2 () from /usr/lib/libc.so.6
Post by Curtis Yarvin
That's extremely peculiar to say the least! I think we run fine in Arch.
Or I thought so.
What would help is a stack trace. You can get a good trace by setting
DEBUG=yes in the Makefile, then running gdb or lldb on the core.
Sent from my iPhone
Now running urbit -c mycomet returns tried to create, but mycomet already exists
~
urbit: home is mycomet
loom: mapped 2048MB
protected loom
live: logical boot
boot: installed 229 jets
boot: loading /home/matt/aur/urbit-git/src/urbit/urb/urbit.pill
arvo: time: ~2015.11.7..18.20.12..03f0
bail: oops
Aborted (core dumped)
I have an Arch droplet running on DigitalOcean with 1GB RAM and a 2GB swap file.
~
urbit: home is mycomet
loom: mapped 2048MB
boot: installed 229 jets
boot: loading /home/matt/aur/urbit-git/src/urbit/urb/urbit.pill
arvo: time: ~2015.11.7..18.08.29..6daf
bail: oops
Aborted (core dumped)
Is there something else I need to do in order to create an urbit?
Thank you very much.
--
You received this message because you are subscribed to the Google Groups "urbit" group.
To unsubscribe from this group and stop receiving emails from it, send an
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups "urbit" group.
To unsubscribe from this group and stop receiving emails from it, send an email to urbit-dev+***@googlegroups.com.
To post to this group, send email to urbit-***@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Curtis Yarvin
2015-11-07 19:08:45 UTC
Permalink
Agh. Unfortunately we use segv internally, you have to set gdb to pass it to the program. Or better, reproduce your core dump with the debug build, then run gdb on the core file to show where it crashed.

Sent from my iPhone
Post by Matthew Piziak
Starting program: /home/matt/aur/urbit-git/src/urbit/bin/urbit -c mycomet
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/usr/lib/libthread_db.so.1".
~
urbit: home is mycomet
loom: mapped 2048MB
Program received signal SIGSEGV, Segmentation fault.
0x00007ffff5df6af4 in __memset_sse2 () from /usr/lib/libc.so.6
Post by Curtis Yarvin
That's extremely peculiar to say the least! I think we run fine in Arch. Or I thought so.
What would help is a stack trace. You can get a good trace by setting DEBUG=yes in the Makefile, then running gdb or lldb on the core.
Sent from my iPhone
Now running urbit -c mycomet returns tried to create, but mycomet already exists
~
urbit: home is mycomet
loom: mapped 2048MB
protected loom
live: logical boot
boot: installed 229 jets
boot: loading /home/matt/aur/urbit-git/src/urbit/urb/urbit.pill
arvo: time: ~2015.11.7..18.20.12..03f0
bail: oops
Aborted (core dumped)
I have an Arch droplet running on DigitalOcean with 1GB RAM and a 2GB swap file.
~
urbit: home is mycomet
loom: mapped 2048MB
boot: installed 229 jets
boot: loading /home/matt/aur/urbit-git/src/urbit/urb/urbit.pill
arvo: time: ~2015.11.7..18.08.29..6daf
bail: oops
Aborted (core dumped)
Is there something else I need to do in order to create an urbit?
Thank you very much.
--
You received this message because you are subscribed to the Google Groups "urbit" group.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups "urbit" group.
To unsubscribe from this group and stop receiving emails from it, send an email to urbit-dev+***@googlegroups.com.
To post to this group, send email to urbit-***@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Matthew Piziak
2015-11-07 19:17:05 UTC
Permalink
Okay. I'm going to be trying a few things one by one. The first is to first
pass handle SIGSEGV pass nostop noprint before run -c mycomet. Here is the
output.

Starting program: /home/matt/aur/urbit-git/src/urbit/bin/urbit -c mycomet
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/usr/lib/libthread_db.so.1".
~
urbit: home is mycomet
loom: mapped 2048MB
boot: installed 229 jets
boot: loading /home/matt/aur/urbit-git/src/urbit/urb/urbit.pill
arvo: time: ~2015.11.7..19.15.03..f134

bail: oops

Program received signal SIGABRT, Aborted.
0x00007ffff5da55f8 in raise () from /usr/lib/libc.so.6
Post by Curtis Yarvin
Agh. Unfortunately we use segv internally, you have to set gdb to pass it
to the program. Or better, reproduce your core dump with the debug build,
then run gdb on the core file to show where it crashed.
Sent from my iPhone
Starting program: /home/matt/aur/urbit-git/src/urbit/bin/urbit -c mycomet
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/usr/lib/libthread_db.so.1".
~
urbit: home is mycomet
loom: mapped 2048MB
Program received signal SIGSEGV, Segmentation fault.
0x00007ffff5df6af4 in __memset_sse2 () from /usr/lib/libc.so.6
Post by Curtis Yarvin
That's extremely peculiar to say the least! I think we run fine in
Arch. Or I thought so.
What would help is a stack trace. You can get a good trace by setting
DEBUG=yes in the Makefile, then running gdb or lldb on the core.
Sent from my iPhone
Now running urbit -c mycomet returns tried to create, but mycomet already exists
~
urbit: home is mycomet
loom: mapped 2048MB
protected loom
live: logical boot
boot: installed 229 jets
boot: loading /home/matt/aur/urbit-git/src/urbit/urb/urbit.pill
arvo: time: ~2015.11.7..18.20.12..03f0
bail: oops
Aborted (core dumped)
I have an Arch droplet running on DigitalOcean with 1GB RAM and a 2GB swap file.
~
urbit: home is mycomet
loom: mapped 2048MB
boot: installed 229 jets
boot: loading /home/matt/aur/urbit-git/src/urbit/urb/urbit.pill
arvo: time: ~2015.11.7..18.08.29..6daf
bail: oops
Aborted (core dumped)
Is there something else I need to do in order to create an urbit?
Thank you very much.
--
You received this message because you are subscribed to the Google Groups "urbit" group.
To unsubscribe from this group and stop receiving emails from it, send an
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups "urbit" group.
To unsubscribe from this group and stop receiving emails from it, send an email to urbit-dev+***@googlegroups.com.
To post to this group, send email to urbit-***@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Matthew Piziak
2015-11-07 19:18:58 UTC
Permalink
If I also handle SIGABRT in the same way, I get the following output:

Starting program: /home/matt/aur/urbit-git/src/urbit/bin/urbit -c mycomet
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/usr/lib/libthread_db.so.1".
~
urbit: home is mycomet
loom: mapped 2048MB
boot: installed 229 jets
boot: loading /home/matt/aur/urbit-git/src/urbit/urb/urbit.pill
arvo: time: ~2015.11.7..19.18.08..9642

bail: oops

Program terminated with signal SIGABRT, Aborted.
The program no longer exists.
Post by Matthew Piziak
Okay. I'm going to be trying a few things one by one. The first is to
first pass handle SIGSEGV pass nostop noprint before run -c mycomet. Here
is the output.
Starting program: /home/matt/aur/urbit-git/src/urbit/bin/urbit -c mycomet
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/usr/lib/libthread_db.so.1".
~
urbit: home is mycomet
loom: mapped 2048MB
boot: installed 229 jets
boot: loading /home/matt/aur/urbit-git/src/urbit/urb/urbit.pill
arvo: time: ~2015.11.7..19.15.03..f134
bail: oops
Program received signal SIGABRT, Aborted.
0x00007ffff5da55f8 in raise () from /usr/lib/libc.so.6
Post by Curtis Yarvin
Agh. Unfortunately we use segv internally, you have to set gdb to pass
it to the program. Or better, reproduce your core dump with the debug
build, then run gdb on the core file to show where it crashed.
Sent from my iPhone
Starting program: /home/matt/aur/urbit-git/src/urbit/bin/urbit -c mycomet
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/usr/lib/libthread_db.so.1".
~
urbit: home is mycomet
loom: mapped 2048MB
Program received signal SIGSEGV, Segmentation fault.
0x00007ffff5df6af4 in __memset_sse2 () from /usr/lib/libc.so.6
Post by Curtis Yarvin
That's extremely peculiar to say the least! I think we run fine in
Arch. Or I thought so.
What would help is a stack trace. You can get a good trace by setting
DEBUG=yes in the Makefile, then running gdb or lldb on the core.
Sent from my iPhone
Now running urbit -c mycomet returns tried to create, but mycomet already exists
~
urbit: home is mycomet
loom: mapped 2048MB
protected loom
live: logical boot
boot: installed 229 jets
boot: loading /home/matt/aur/urbit-git/src/urbit/urb/urbit.pill
arvo: time: ~2015.11.7..18.20.12..03f0
bail: oops
Aborted (core dumped)
I have an Arch droplet running on DigitalOcean with 1GB RAM and a 2GB swap file.
~
urbit: home is mycomet
loom: mapped 2048MB
boot: installed 229 jets
boot: loading /home/matt/aur/urbit-git/src/urbit/urb/urbit.pill
arvo: time: ~2015.11.7..18.08.29..6daf
bail: oops
Aborted (core dumped)
Is there something else I need to do in order to create an urbit?
Thank you very much.
--
You received this message because you are subscribed to the Google
Groups "urbit" group.
To unsubscribe from this group and stop receiving emails from it, send
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups "urbit" group.
To unsubscribe from this group and stop receiving emails from it, send an email to urbit-dev+***@googlegroups.com.
To post to this group, send email to urbit-***@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Matthew Piziak
2015-11-07 19:23:42 UTC
Permalink
If I run

gdb bin/urbit
/var/lib/systemd/coredump/core.urbit.1000.693c327158ee49d18bccf08332d383db.7609.1446924010000000.lz4

I get the following output:

Reading symbols from bin/urbit...done.
"/var/lib/systemd/coredump/core.urbit.1000.693c327158ee49d18bccf08332d383db.7609.1446924010000000.lz4"
is not a core dump: File format not recognized
Post by Matthew Piziak
Starting program: /home/matt/aur/urbit-git/src/urbit/bin/urbit -c mycomet
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/usr/lib/libthread_db.so.1".
~
urbit: home is mycomet
loom: mapped 2048MB
boot: installed 229 jets
boot: loading /home/matt/aur/urbit-git/src/urbit/urb/urbit.pill
arvo: time: ~2015.11.7..19.18.08..9642
bail: oops
Program terminated with signal SIGABRT, Aborted.
The program no longer exists.
Post by Matthew Piziak
Okay. I'm going to be trying a few things one by one. The first is to
first pass handle SIGSEGV pass nostop noprint before run -c mycomet.
Here is the output.
Starting program: /home/matt/aur/urbit-git/src/urbit/bin/urbit -c mycomet
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/usr/lib/libthread_db.so.1".
~
urbit: home is mycomet
loom: mapped 2048MB
boot: installed 229 jets
boot: loading /home/matt/aur/urbit-git/src/urbit/urb/urbit.pill
arvo: time: ~2015.11.7..19.15.03..f134
bail: oops
Program received signal SIGABRT, Aborted.
0x00007ffff5da55f8 in raise () from /usr/lib/libc.so.6
Post by Curtis Yarvin
Agh. Unfortunately we use segv internally, you have to set gdb to pass
it to the program. Or better, reproduce your core dump with the debug
build, then run gdb on the core file to show where it crashed.
Sent from my iPhone
Starting program: /home/matt/aur/urbit-git/src/urbit/bin/urbit -c mycomet
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/usr/lib/libthread_db.so.1".
~
urbit: home is mycomet
loom: mapped 2048MB
Program received signal SIGSEGV, Segmentation fault.
0x00007ffff5df6af4 in __memset_sse2 () from /usr/lib/libc.so.6
Post by Curtis Yarvin
That's extremely peculiar to say the least! I think we run fine in
Arch. Or I thought so.
What would help is a stack trace. You can get a good trace by setting
DEBUG=yes in the Makefile, then running gdb or lldb on the core.
Sent from my iPhone
Now running urbit -c mycomet returns tried to create, but mycomet already exists
~
urbit: home is mycomet
loom: mapped 2048MB
protected loom
live: logical boot
boot: installed 229 jets
boot: loading /home/matt/aur/urbit-git/src/urbit/urb/urbit.pill
arvo: time: ~2015.11.7..18.20.12..03f0
bail: oops
Aborted (core dumped)
I have an Arch droplet running on DigitalOcean with 1GB RAM and a 2GB swap file.
~
urbit: home is mycomet
loom: mapped 2048MB
boot: installed 229 jets
boot: loading /home/matt/aur/urbit-git/src/urbit/urb/urbit.pill
arvo: time: ~2015.11.7..18.08.29..6daf
bail: oops
Aborted (core dumped)
Is there something else I need to do in order to create an urbit?
Thank you very much.
--
You received this message because you are subscribed to the Google
Groups "urbit" group.
To unsubscribe from this group and stop receiving emails from it, send
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups "urbit" group.
To unsubscribe from this group and stop receiving emails from it, send an email to urbit-dev+***@googlegroups.com.
To post to this group, send email to urbit-***@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Curtis Yarvin
2015-11-07 19:54:02 UTC
Permalink
From the lz4 suffix, I'm guessing systemd has done something awful to compress your core. I'd copy it out of there and decompress it. Sorry for the trouble!

Sent from my iPhone
Post by Matthew Piziak
If I run
gdb bin/urbit /var/lib/systemd/coredump/core.urbit.1000.693c327158ee49d18bccf08332d383db.7609.1446924010000000.lz4
Reading symbols from bin/urbit...done.
"/var/lib/systemd/coredump/core.urbit.1000.693c327158ee49d18bccf08332d383db.7609.1446924010000000.lz4" is not a core dump: File format not recognized
Post by Matthew Piziak
Starting program: /home/matt/aur/urbit-git/src/urbit/bin/urbit -c mycomet
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/usr/lib/libthread_db.so.1".
~
urbit: home is mycomet
loom: mapped 2048MB
boot: installed 229 jets
boot: loading /home/matt/aur/urbit-git/src/urbit/urb/urbit.pill
arvo: time: ~2015.11.7..19.18.08..9642
bail: oops
Program terminated with signal SIGABRT, Aborted.
The program no longer exists.
Okay. I'm going to be trying a few things one by one. The first is to first pass handle SIGSEGV pass nostop noprint before run -c mycomet. Here is the output.
Starting program: /home/matt/aur/urbit-git/src/urbit/bin/urbit -c mycomet
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/usr/lib/libthread_db.so.1".
~
urbit: home is mycomet
loom: mapped 2048MB
boot: installed 229 jets
boot: loading /home/matt/aur/urbit-git/src/urbit/urb/urbit.pill
arvo: time: ~2015.11.7..19.15.03..f134
bail: oops
Program received signal SIGABRT, Aborted.
0x00007ffff5da55f8 in raise () from /usr/lib/libc.so.6
Post by Curtis Yarvin
Agh. Unfortunately we use segv internally, you have to set gdb to pass it to the program. Or better, reproduce your core dump with the debug build, then run gdb on the core file to show where it crashed.
Sent from my iPhone
Post by Matthew Piziak
Starting program: /home/matt/aur/urbit-git/src/urbit/bin/urbit -c mycomet
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/usr/lib/libthread_db.so.1".
~
urbit: home is mycomet
loom: mapped 2048MB
Program received signal SIGSEGV, Segmentation fault.
0x00007ffff5df6af4 in __memset_sse2 () from /usr/lib/libc.so.6
Post by Curtis Yarvin
That's extremely peculiar to say the least! I think we run fine in Arch. Or I thought so.
What would help is a stack trace. You can get a good trace by setting DEBUG=yes in the Makefile, then running gdb or lldb on the core.
Sent from my iPhone
Now running urbit -c mycomet returns tried to create, but mycomet already exists
~
urbit: home is mycomet
loom: mapped 2048MB
protected loom
live: logical boot
boot: installed 229 jets
boot: loading /home/matt/aur/urbit-git/src/urbit/urb/urbit.pill
arvo: time: ~2015.11.7..18.20.12..03f0
bail: oops
Aborted (core dumped)
I have an Arch droplet running on DigitalOcean with 1GB RAM and a 2GB swap file.
~
urbit: home is mycomet
loom: mapped 2048MB
boot: installed 229 jets
boot: loading /home/matt/aur/urbit-git/src/urbit/urb/urbit.pill
arvo: time: ~2015.11.7..18.08.29..6daf
bail: oops
Aborted (core dumped)
Is there something else I need to do in order to create an urbit?
Thank you very much.
--
You received this message because you are subscribed to the Google Groups "urbit" group.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups "urbit" group.
To unsubscribe from this group and stop receiving emails from it, send an email to urbit-dev+***@googlegroups.com.
To post to this group, send email to urbit-***@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Matthew Piziak
2015-11-07 20:41:46 UTC
Permalink
Not at all; thanks for helping. Unfortunately I can't seem to lz4c -d the
core dump file. Output:

Error 44 : Unrecognized header : file cannot be decoded
Post by Curtis Yarvin
From the lz4 suffix, I'm guessing systemd has done something awful to
compress your core. I'd copy it out of there and decompress it. Sorry for
the trouble!
Sent from my iPhone
If I run
gdb bin/urbit
/var/lib/systemd/coredump/core.urbit.1000.693c327158ee49d18bccf08332d383db.7609.1446924010000000.lz4
Reading symbols from bin/urbit...done.
"/var/lib/systemd/coredump/core.urbit.1000.693c327158ee49d18bccf08332d383db.7609.1446924010000000.lz4"
is not a core dump: File format not recognized
Post by Matthew Piziak
Starting program: /home/matt/aur/urbit-git/src/urbit/bin/urbit -c mycomet
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/usr/lib/libthread_db.so.1".
~
urbit: home is mycomet
loom: mapped 2048MB
boot: installed 229 jets
boot: loading /home/matt/aur/urbit-git/src/urbit/urb/urbit.pill
arvo: time: ~2015.11.7..19.18.08..9642
bail: oops
Program terminated with signal SIGABRT, Aborted.
The program no longer exists.
Post by Matthew Piziak
Okay. I'm going to be trying a few things one by one. The first is to
first pass handle SIGSEGV pass nostop noprint before run -c mycomet.
Here is the output.
Starting program: /home/matt/aur/urbit-git/src/urbit/bin/urbit -c mycomet
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/usr/lib/libthread_db.so.1".
~
urbit: home is mycomet
loom: mapped 2048MB
boot: installed 229 jets
boot: loading /home/matt/aur/urbit-git/src/urbit/urb/urbit.pill
arvo: time: ~2015.11.7..19.15.03..f134
bail: oops
Program received signal SIGABRT, Aborted.
0x00007ffff5da55f8 in raise () from /usr/lib/libc.so.6
Post by Curtis Yarvin
Agh. Unfortunately we use segv internally, you have to set gdb to pass
it to the program. Or better, reproduce your core dump with the debug
build, then run gdb on the core file to show where it crashed.
Sent from my iPhone
Starting program: /home/matt/aur/urbit-git/src/urbit/bin/urbit -c mycomet
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/usr/lib/libthread_db.so.1".
~
urbit: home is mycomet
loom: mapped 2048MB
Program received signal SIGSEGV, Segmentation fault.
0x00007ffff5df6af4 in __memset_sse2 () from /usr/lib/libc.so.6
Post by Curtis Yarvin
That's extremely peculiar to say the least! I think we run fine in
Arch. Or I thought so.
What would help is a stack trace. You can get a good trace by setting
DEBUG=yes in the Makefile, then running gdb or lldb on the core.
Sent from my iPhone
Now running urbit -c mycomet returns tried to create, but mycomet already exists
~
urbit: home is mycomet
loom: mapped 2048MB
protected loom
live: logical boot
boot: installed 229 jets
boot: loading /home/matt/aur/urbit-git/src/urbit/urb/urbit.pill
arvo: time: ~2015.11.7..18.20.12..03f0
bail: oops
Aborted (core dumped)
I have an Arch droplet running on DigitalOcean with 1GB RAM and a 2GB swap file.
~
urbit: home is mycomet
loom: mapped 2048MB
boot: installed 229 jets
boot: loading /home/matt/aur/urbit-git/src/urbit/urb/urbit.pill
arvo: time: ~2015.11.7..18.08.29..6daf
bail: oops
Aborted (core dumped)
Is there something else I need to do in order to create an urbit?
Thank you very much.
--
You received this message because you are subscribed to the Google
Groups "urbit" group.
To unsubscribe from this group and stop receiving emails from it, send
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups "urbit" group.
To unsubscribe from this group and stop receiving emails from it, send an email to urbit-dev+***@googlegroups.com.
To post to this group, send email to urbit-***@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Curtis Yarvin
2015-11-07 20:46:46 UTC
Permalink
I don't know arch, but it seems like this page should be helpful:

https://wiki.archlinux.org/index.php/Core_dump

"coredumpctl" indeed. What is Unix coming to? :-)

On Sat, Nov 7, 2015 at 12:41 PM, Matthew Piziak
Post by Matthew Piziak
Not at all; thanks for helping. Unfortunately I can't seem to lz4c -d the
Error 44 : Unrecognized header : file cannot be decoded
Post by Curtis Yarvin
From the lz4 suffix, I'm guessing systemd has done something awful to
compress your core. I'd copy it out of there and decompress it. Sorry for
the trouble!
Sent from my iPhone
If I run
gdb bin/urbit
/var/lib/systemd/coredump/core.urbit.1000.693c327158ee49d18bccf08332d383db.7609.1446924010000000.lz4
Reading symbols from bin/urbit...done.
"/var/lib/systemd/coredump/core.urbit.1000.693c327158ee49d18bccf08332d383db.7609.1446924010000000.lz4"
is not a core dump: File format not recognized
Post by Matthew Piziak
Starting program: /home/matt/aur/urbit-git/src/urbit/bin/urbit -c mycomet
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/usr/lib/libthread_db.so.1".
~
urbit: home is mycomet
loom: mapped 2048MB
boot: installed 229 jets
boot: loading /home/matt/aur/urbit-git/src/urbit/urb/urbit.pill
arvo: time: ~2015.11.7..19.18.08..9642
bail: oops
Program terminated with signal SIGABRT, Aborted.
The program no longer exists.
Post by Matthew Piziak
Okay. I'm going to be trying a few things one by one. The first is to
first pass handle SIGSEGV pass nostop noprint before run -c mycomet. Here is
the output.
Starting program: /home/matt/aur/urbit-git/src/urbit/bin/urbit -c mycomet
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/usr/lib/libthread_db.so.1".
~
urbit: home is mycomet
loom: mapped 2048MB
boot: installed 229 jets
boot: loading /home/matt/aur/urbit-git/src/urbit/urb/urbit.pill
arvo: time: ~2015.11.7..19.15.03..f134
bail: oops
Program received signal SIGABRT, Aborted.
0x00007ffff5da55f8 in raise () from /usr/lib/libc.so.6
Post by Curtis Yarvin
Agh. Unfortunately we use segv internally, you have to set gdb to pass
it to the program. Or better, reproduce your core dump with the debug
build, then run gdb on the core file to show where it crashed.
Sent from my iPhone
Starting program: /home/matt/aur/urbit-git/src/urbit/bin/urbit -c mycomet
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/usr/lib/libthread_db.so.1".
~
urbit: home is mycomet
loom: mapped 2048MB
Program received signal SIGSEGV, Segmentation fault.
0x00007ffff5df6af4 in __memset_sse2 () from /usr/lib/libc.so.6
Post by Curtis Yarvin
That's extremely peculiar to say the least! I think we run fine in
Arch. Or I thought so.
What would help is a stack trace. You can get a good trace by setting
DEBUG=yes in the Makefile, then running gdb or lldb on the core.
Sent from my iPhone
Now running urbit -c mycomet returns tried to create, but mycomet already exists
~
urbit: home is mycomet
loom: mapped 2048MB
protected loom
live: logical boot
boot: installed 229 jets
boot: loading /home/matt/aur/urbit-git/src/urbit/urb/urbit.pill
arvo: time: ~2015.11.7..18.20.12..03f0
bail: oops
Aborted (core dumped)
Post by Matthew Piziak
I have an Arch droplet running on DigitalOcean with 1GB RAM and a 2GB
swap file.
~
urbit: home is mycomet
loom: mapped 2048MB
boot: installed 229 jets
boot: loading /home/matt/aur/urbit-git/src/urbit/urb/urbit.pill
arvo: time: ~2015.11.7..18.08.29..6daf
bail: oops
Aborted (core dumped)
Is there something else I need to do in order to create an urbit?
Thank you very much.
--
You received this message because you are subscribed to the Google
Groups "urbit" group.
To unsubscribe from this group and stop receiving emails from it, send
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups "urbit" group.
To unsubscribe from this group and stop receiving emails from it, send an email to urbit-dev+***@googlegroups.com.
To post to this group, send email to urbit-***@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Raymond Pasco
2015-11-07 20:49:42 UTC
Permalink
Hey, only Linux has that nonsense (and the kernel doesn't endorse it)!
Yours,
r
--
You received this message because you are subscribed to the Google Groups "urbit" group.
To unsubscribe from this group and stop receiving emails from it, send an email to urbit-dev+***@googlegroups.com.
To post to this group, send email to urbit-***@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Matthew Piziak
2015-11-07 21:05:10 UTC
Permalink
Thanks! Here are the results:

PID: 8053 (urbit)
UID: 1000 (matt)
GID: 1000 (matt)
Signal: 6 (ABRT)
Timestamp: Sat 2015-11-07 21:01:55 UTC (54s ago)
Command Line: bin/urbit -c mycomet
Executable: /home/matt/aur/urbit-git/src/urbit/bin/urbit
Control Group: /user.slice/user-1000.slice/session-c53.scope
Unit: session-c53.scope
Slice: user-1000.slice
Session: c53
Owner UID: 1000 (matt)
Boot ID: 693c327158ee49d18bccf08332d383db
Machine ID: 2f07f9cab2c74121bec370952ee69db4
Hostname: corvus
Coredump:
/var/lib/systemd/coredump/core.urbit.1000.693c327158ee49d18bccf08332d383db.8053.1446930115000000.lz4
Message: Process 8053 (urbit) of user 1000 dumped core

Reading symbols from /home/matt/aur/urbit-git/src/urbit/bin/urbit...done.
[New LWP 8053]

warning: Could not load shared library symbols for linux-vdso.so.1.
Do you need "set solib-search-path" or "set sysroot"?
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/usr/lib/libthread_db.so.1".
Core was generated by `bin/urbit -c mycomet'.
Program terminated with signal SIGABRT, Aborted.
#0 0x00007f8bd2ea75f8 in raise () from /usr/lib/libc.so.6
Post by Raymond Pasco
Hey, only Linux has that nonsense (and the kernel doesn't endorse it)!
Yours,
r
--
You received this message because you are subscribed to the Google Groups "urbit" group.
To unsubscribe from this group and stop receiving emails from it, send an email to urbit-dev+***@googlegroups.com.
To post to this group, send email to urbit-***@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Charlie Cummings
2015-11-07 21:13:38 UTC
Permalink
I run Arch on both my laptop and desktop, and urbit runs fine on both
circa two days ago. I haven't been available since then, but unless
the sist patch broke everything, it should work.
Post by Matthew Piziak
PID: 8053 (urbit)
UID: 1000 (matt)
GID: 1000 (matt)
Signal: 6 (ABRT)
Timestamp: Sat 2015-11-07 21:01:55 UTC (54s ago)
Command Line: bin/urbit -c mycomet
Executable: /home/matt/aur/urbit-git/src/urbit/bin/urbit
Control Group: /user.slice/user-1000.slice/session-c53.scope
Unit: session-c53.scope
Slice: user-1000.slice
Session: c53
Owner UID: 1000 (matt)
Boot ID: 693c327158ee49d18bccf08332d383db
Machine ID: 2f07f9cab2c74121bec370952ee69db4
Hostname: corvus
/var/lib/systemd/coredump/core.urbit.1000.693c327158ee49d18bccf08332d383db.8053.1446930115000000.lz4
Message: Process 8053 (urbit) of user 1000 dumped core
Reading symbols from /home/matt/aur/urbit-git/src/urbit/bin/urbit...done.
[New LWP 8053]
warning: Could not load shared library symbols for linux-vdso.so.1.
Do you need "set solib-search-path" or "set sysroot"?
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/usr/lib/libthread_db.so.1".
Core was generated by `bin/urbit -c mycomet'.
Program terminated with signal SIGABRT, Aborted.
#0 0x00007f8bd2ea75f8 in raise () from /usr/lib/libc.so.6
Post by Raymond Pasco
Hey, only Linux has that nonsense (and the kernel doesn't endorse it)!
Yours,
r
--
You received this message because you are subscribed to the Google Groups "urbit" group.
To unsubscribe from this group and stop receiving emails from it, send an
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups "urbit" group.
To unsubscribe from this group and stop receiving emails from it, send an email to urbit-dev+***@googlegroups.com.
To post to this group, send email to urbit-***@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Curtis Yarvin
2015-11-07 21:55:02 UTC
Permalink
I think you need to type 'bt' or 'where' to show the full trace stack.
You may also be in a different thread, so 'bt all'? I know an
exception is being raised, but #0 doesn't help me much...
Post by Matthew Piziak
PID: 8053 (urbit)
UID: 1000 (matt)
GID: 1000 (matt)
Signal: 6 (ABRT)
Timestamp: Sat 2015-11-07 21:01:55 UTC (54s ago)
Command Line: bin/urbit -c mycomet
Executable: /home/matt/aur/urbit-git/src/urbit/bin/urbit
Control Group: /user.slice/user-1000.slice/session-c53.scope
Unit: session-c53.scope
Slice: user-1000.slice
Session: c53
Owner UID: 1000 (matt)
Boot ID: 693c327158ee49d18bccf08332d383db
Machine ID: 2f07f9cab2c74121bec370952ee69db4
Hostname: corvus
/var/lib/systemd/coredump/core.urbit.1000.693c327158ee49d18bccf08332d383db.8053.1446930115000000.lz4
Message: Process 8053 (urbit) of user 1000 dumped core
Reading symbols from /home/matt/aur/urbit-git/src/urbit/bin/urbit...done.
[New LWP 8053]
warning: Could not load shared library symbols for linux-vdso.so.1.
Do you need "set solib-search-path" or "set sysroot"?
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/usr/lib/libthread_db.so.1".
Core was generated by `bin/urbit -c mycomet'.
Program terminated with signal SIGABRT, Aborted.
#0 0x00007f8bd2ea75f8 in raise () from /usr/lib/libc.so.6
Post by Raymond Pasco
Hey, only Linux has that nonsense (and the kernel doesn't endorse it)!
Yours,
r
--
You received this message because you are subscribed to the Google Groups "urbit" group.
To unsubscribe from this group and stop receiving emails from it, send an email to urbit-dev+***@googlegroups.com.
To post to this group, send email to urbit-***@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Raymond Pasco
2015-11-07 22:03:28 UTC
Permalink
'thread apply all bt full' should be com prehensive.
Yours,
r
--
You received this message because you are subscribed to the Google Groups "urbit" group.
To unsubscribe from this group and stop receiving emails from it, send an email to urbit-dev+***@googlegroups.com.
To post to this group, send email to urbit-***@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Matthew Piziak
2015-11-07 22:46:02 UTC
Permalink
Thanks for bearing with me. Here's the output of thread apply all bt full:

Thread 1 (Thread 0x7f8bd50ee740 (LWP 8053)):
#0 0x00007f8bd2ea75f8 in raise () from /usr/lib/libc.so.6
No symbol table info available.
#1 0x00007f8bd2ea8a7a in abort () from /usr/lib/libc.so.6
No symbol table info available.
#2 0x0000000000418fdb in u3m_bail (how=1936748399) at noun/manage.c:613
__PRETTY_FUNCTION__ = "u3m_bail"
#3 0x00000000004190e9 in c3_cooked () at noun/manage.c:650
No locals.
#4 0x00000000004612df in u3_term_io_init () at vere/term.c:135
len_w = 0
uty_u = 0x1274f30
__PRETTY_FUNCTION__ = "u3_term_io_init"
#5 0x0000000000455940 in _lo_init () at vere/loop.c:180
cod_l = 0
#6 0x00000000004560b1 in u3_lo_loop () at vere/loop.c:646
lup_u = 0x786660 <default_loop_struct>
#7 0x000000000044e4b2 in main (argc=3, argv=0x7ffe7509fef8)
at vere/main.c:454
No locals.
Post by Raymond Pasco
'thread apply all bt full' should be com prehensive.
Yours,
r
--
You received this message because you are subscribed to the Google Groups "urbit" group.
To unsubscribe from this group and stop receiving emails from it, send an email to urbit-dev+***@googlegroups.com.
To post to this group, send email to urbit-***@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Curtis Yarvin
2015-11-08 00:23:27 UTC
Permalink
Hmm, that's not very user-friendly of us, but it looks like your
terminfo doesn't export the `kcuu1` (up arrow) resource. Of course we
could report this in a much nicer way; I've just edited the code to do
so.

Terminal handling is the cloaca maxima of Unix and unfortunately I am
not a terminfo wizard, but perhaps you can to some extent take it from
here. What is your TERM variable set to? What terminal are you
using? Bad terminal, no biscuit...
Post by Matthew Piziak
#0 0x00007f8bd2ea75f8 in raise () from /usr/lib/libc.so.6
No symbol table info available.
#1 0x00007f8bd2ea8a7a in abort () from /usr/lib/libc.so.6
No symbol table info available.
#2 0x0000000000418fdb in u3m_bail (how=1936748399) at noun/manage.c:613
__PRETTY_FUNCTION__ = "u3m_bail"
#3 0x00000000004190e9 in c3_cooked () at noun/manage.c:650
No locals.
#4 0x00000000004612df in u3_term_io_init () at vere/term.c:135
len_w = 0
uty_u = 0x1274f30
__PRETTY_FUNCTION__ = "u3_term_io_init"
#5 0x0000000000455940 in _lo_init () at vere/loop.c:180
cod_l = 0
#6 0x00000000004560b1 in u3_lo_loop () at vere/loop.c:646
lup_u = 0x786660 <default_loop_struct>
#7 0x000000000044e4b2 in main (argc=3, argv=0x7ffe7509fef8)
at vere/main.c:454
No locals.
Post by Raymond Pasco
'thread apply all bt full' should be com prehensive.
Yours,
r
--
You received this message because you are subscribed to the Google Groups "urbit" group.
To unsubscribe from this group and stop receiving emails from it, send an email to urbit-dev+***@googlegroups.com.
To post to this group, send email to urbit-***@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Matthew Piziak
2015-11-08 01:08:29 UTC
Permalink
It clicked as soon as you mentioned terminfo. Closed Emacs–TRAMP, opened
default OSX terminal and sshed into my remote. Works fine now. Sorry; I
should have tried that first.

Thank you very much for your help!
Post by Curtis Yarvin
Hmm, that's not very user-friendly of us, but it looks like your
terminfo doesn't export the `kcuu1` (up arrow) resource. Of course we
could report this in a much nicer way; I've just edited the code to do
so.
Terminal handling is the cloaca maxima of Unix and unfortunately I am
not a terminfo wizard, but perhaps you can to some extent take it from
here. What is your TERM variable set to? What terminal are you
using? Bad terminal, no biscuit...
Post by Matthew Piziak
Thanks for bearing with me. Here's the output of thread apply all bt
#0 0x00007f8bd2ea75f8 in raise () from /usr/lib/libc.so.6
No symbol table info available.
#1 0x00007f8bd2ea8a7a in abort () from /usr/lib/libc.so.6
No symbol table info available.
#2 0x0000000000418fdb in u3m_bail (how=1936748399) at noun/manage.c:613
__PRETTY_FUNCTION__ = "u3m_bail"
#3 0x00000000004190e9 in c3_cooked () at noun/manage.c:650
No locals.
#4 0x00000000004612df in u3_term_io_init () at vere/term.c:135
len_w = 0
uty_u = 0x1274f30
__PRETTY_FUNCTION__ = "u3_term_io_init"
#5 0x0000000000455940 in _lo_init () at vere/loop.c:180
cod_l = 0
#6 0x00000000004560b1 in u3_lo_loop () at vere/loop.c:646
lup_u = 0x786660 <default_loop_struct>
#7 0x000000000044e4b2 in main (argc=3, argv=0x7ffe7509fef8)
at vere/main.c:454
No locals.
Post by Raymond Pasco
'thread apply all bt full' should be com prehensive.
Yours,
r
--
You received this message because you are subscribed to the Google Groups "urbit" group.
To unsubscribe from this group and stop receiving emails from it, send an email to urbit-dev+***@googlegroups.com.
To post to this group, send email to urbit-***@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Curtis Yarvin
2015-11-07 19:23:51 UTC
Permalink
Definitely don't handle abort the same way! :-)

What I need is just the stack trace at which the abort (oops means an assertion fail) happens.

Sent from my iPhone
Post by Matthew Piziak
Starting program: /home/matt/aur/urbit-git/src/urbit/bin/urbit -c mycomet
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/usr/lib/libthread_db.so.1".
~
urbit: home is mycomet
loom: mapped 2048MB
boot: installed 229 jets
boot: loading /home/matt/aur/urbit-git/src/urbit/urb/urbit.pill
arvo: time: ~2015.11.7..19.18.08..9642
bail: oops
Program terminated with signal SIGABRT, Aborted.
The program no longer exists.
Okay. I'm going to be trying a few things one by one. The first is to first pass handle SIGSEGV pass nostop noprint before run -c mycomet. Here is the output.
Starting program: /home/matt/aur/urbit-git/src/urbit/bin/urbit -c mycomet
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/usr/lib/libthread_db.so.1".
~
urbit: home is mycomet
loom: mapped 2048MB
boot: installed 229 jets
boot: loading /home/matt/aur/urbit-git/src/urbit/urb/urbit.pill
arvo: time: ~2015.11.7..19.15.03..f134
bail: oops
Program received signal SIGABRT, Aborted.
0x00007ffff5da55f8 in raise () from /usr/lib/libc.so.6
Post by Curtis Yarvin
Agh. Unfortunately we use segv internally, you have to set gdb to pass it to the program. Or better, reproduce your core dump with the debug build, then run gdb on the core file to show where it crashed.
Sent from my iPhone
Post by Matthew Piziak
Starting program: /home/matt/aur/urbit-git/src/urbit/bin/urbit -c mycomet
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/usr/lib/libthread_db.so.1".
~
urbit: home is mycomet
loom: mapped 2048MB
Program received signal SIGSEGV, Segmentation fault.
0x00007ffff5df6af4 in __memset_sse2 () from /usr/lib/libc.so.6
Post by Curtis Yarvin
That's extremely peculiar to say the least! I think we run fine in Arch. Or I thought so.
What would help is a stack trace. You can get a good trace by setting DEBUG=yes in the Makefile, then running gdb or lldb on the core.
Sent from my iPhone
Now running urbit -c mycomet returns tried to create, but mycomet already exists
~
urbit: home is mycomet
loom: mapped 2048MB
protected loom
live: logical boot
boot: installed 229 jets
boot: loading /home/matt/aur/urbit-git/src/urbit/urb/urbit.pill
arvo: time: ~2015.11.7..18.20.12..03f0
bail: oops
Aborted (core dumped)
I have an Arch droplet running on DigitalOcean with 1GB RAM and a 2GB swap file.
~
urbit: home is mycomet
loom: mapped 2048MB
boot: installed 229 jets
boot: loading /home/matt/aur/urbit-git/src/urbit/urb/urbit.pill
arvo: time: ~2015.11.7..18.08.29..6daf
bail: oops
Aborted (core dumped)
Is there something else I need to do in order to create an urbit?
Thank you very much.
--
You received this message because you are subscribed to the Google Groups "urbit" group.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups "urbit" group.
To unsubscribe from this group and stop receiving emails from it, send an email to urbit-dev+***@googlegroups.com.
To post to this group, send email to urbit-***@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Matthew Piziak
2015-11-07 19:26:08 UTC
Permalink
Thanks. Do you know why gdb isn't recognizing my coredump file?
Post by Curtis Yarvin
Definitely don't handle abort the same way! :-)
What I need is just the stack trace at which the abort (oops means an
assertion fail) happens.
Sent from my iPhone
Starting program: /home/matt/aur/urbit-git/src/urbit/bin/urbit -c mycomet
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/usr/lib/libthread_db.so.1".
~
urbit: home is mycomet
loom: mapped 2048MB
boot: installed 229 jets
boot: loading /home/matt/aur/urbit-git/src/urbit/urb/urbit.pill
arvo: time: ~2015.11.7..19.18.08..9642
bail: oops
Program terminated with signal SIGABRT, Aborted.
The program no longer exists.
Post by Matthew Piziak
Okay. I'm going to be trying a few things one by one. The first is to
first pass handle SIGSEGV pass nostop noprint before run -c mycomet.
Here is the output.
Starting program: /home/matt/aur/urbit-git/src/urbit/bin/urbit -c mycomet
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/usr/lib/libthread_db.so.1".
~
urbit: home is mycomet
loom: mapped 2048MB
boot: installed 229 jets
boot: loading /home/matt/aur/urbit-git/src/urbit/urb/urbit.pill
arvo: time: ~2015.11.7..19.15.03..f134
bail: oops
Program received signal SIGABRT, Aborted.
0x00007ffff5da55f8 in raise () from /usr/lib/libc.so.6
Post by Curtis Yarvin
Agh. Unfortunately we use segv internally, you have to set gdb to pass
it to the program. Or better, reproduce your core dump with the debug
build, then run gdb on the core file to show where it crashed.
Sent from my iPhone
Starting program: /home/matt/aur/urbit-git/src/urbit/bin/urbit -c mycomet
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/usr/lib/libthread_db.so.1".
~
urbit: home is mycomet
loom: mapped 2048MB
Program received signal SIGSEGV, Segmentation fault.
0x00007ffff5df6af4 in __memset_sse2 () from /usr/lib/libc.so.6
Post by Curtis Yarvin
That's extremely peculiar to say the least! I think we run fine in
Arch. Or I thought so.
What would help is a stack trace. You can get a good trace by setting
DEBUG=yes in the Makefile, then running gdb or lldb on the core.
Sent from my iPhone
Now running urbit -c mycomet returns tried to create, but mycomet already exists
~
urbit: home is mycomet
loom: mapped 2048MB
protected loom
live: logical boot
boot: installed 229 jets
boot: loading /home/matt/aur/urbit-git/src/urbit/urb/urbit.pill
arvo: time: ~2015.11.7..18.20.12..03f0
bail: oops
Aborted (core dumped)
I have an Arch droplet running on DigitalOcean with 1GB RAM and a 2GB swap file.
~
urbit: home is mycomet
loom: mapped 2048MB
boot: installed 229 jets
boot: loading /home/matt/aur/urbit-git/src/urbit/urb/urbit.pill
arvo: time: ~2015.11.7..18.08.29..6daf
bail: oops
Aborted (core dumped)
Is there something else I need to do in order to create an urbit?
Thank you very much.
--
You received this message because you are subscribed to the Google
Groups "urbit" group.
To unsubscribe from this group and stop receiving emails from it, send
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups "urbit" group.
To unsubscribe from this group and stop receiving emails from it, send an email to urbit-dev+***@googlegroups.com.
To post to this group, send email to urbit-***@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Loading...