Discussion:
[urbit] boot: loading urbit.pill -- Aborted (core dumped)
Andrew D'Angelo
2016-02-15 21:53:32 UTC
Permalink
Hello,

I'm trying to get started with urbit on Debian Wheezy.
I've tried both installing urbit from the unofficial Debian package and
building from source, both running in a PuTTY session and a forwarded xterm
session. Every time I try bin/urbit -c mycomet I get

***@lyoko:~/downloads/urbit$ bin/urbit -c mycomet
~
urbit: home is mycomet
loom: mapped 2048MB
boot: installed 229 jets
boot: loading /home/excel/downloads/urbit/urb/urbit.pill
Aborted (core dumped)

Any help would be appreciated.
Thank you,
Andrew
--
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
2016-02-15 21:58:35 UTC
Permalink
Sorry, Andrew! Any chance you can produce a stack trace on that
coredump? gdb bin/urbit core should do it, then 'bt' from the gdb
command line. For extra points, change DEBUG=no to DEBUG=yes in
Makefile.

Also, in case you somehow installed a very old version, try `rm -rf
mycomet` first.
Post by Andrew D'Angelo
Hello,
I'm trying to get started with urbit on Debian Wheezy.
I've tried both installing urbit from the unofficial Debian package and
building from source, both running in a PuTTY session and a forwarded xterm
session. Every time I try bin/urbit -c mycomet I get
~
urbit: home is mycomet
loom: mapped 2048MB
boot: installed 229 jets
boot: loading /home/excel/downloads/urbit/urb/urbit.pill
Aborted (core dumped)
Any help would be appreciated.
Thank you,
Andrew
--
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.
Andrew D'Angelo
2016-02-15 22:14:06 UTC
Permalink
Rebuilding urbit with "DEBUG=yes" stops the crash, strangely enough.
Here is the gdb core dump from "DEBUG=no":

Reading symbols from /home/excel/downloads/urbit/bin/urbit...done.
[New LWP 24876]
warning: Can't read pathname for load map: Input/output error.
[Thread debugging using libthread_db enabled]
Using host libthread_db library
"/lib/i386-linux-gnu/i686/cmov/libthread_db.so.1".
Core was generated by `bin/urbit -c mycomet'.
Program terminated with signal 6, Aborted.
#0 0xb776d424 in __kernel_vsyscall ()

(gdb) bt

#0 0xb776d424 in __kernel_vsyscall ()
#1 0xb71d6661 in *__GI_raise (sig=6)
at ../nptl/sysdeps/unix/sysv/linux/raise.c:64
#2 0xb71d9a92 in *__GI_abort ()
at abort.c:92
#3 0x0805deea in u3m_bail ()
#4 0x0806fb19 in _cue_in ()
#5 0x0806fc67 in u3ke_cue ()
#6 0x080647a3 in u3v_make ()
#7 0x0805fd06 in u3m_boot ()
#8 0x0804ed46 in main ()
Post by Curtis Yarvin
Sorry, Andrew! Any chance you can produce a stack trace on that
coredump? gdb bin/urbit core should do it, then 'bt' from the gdb
command line. For extra points, change DEBUG=no to DEBUG=yes in
Makefile.
Also, in case you somehow installed a very old version, try `rm -rf
mycomet` first.
Post by Andrew D'Angelo
Hello,
I'm trying to get started with urbit on Debian Wheezy.
I've tried both installing urbit from the unofficial Debian package and
building from source, both running in a PuTTY session and a forwarded
xterm
Post by Andrew D'Angelo
session. Every time I try bin/urbit -c mycomet I get
~
urbit: home is mycomet
loom: mapped 2048MB
boot: installed 229 jets
boot: loading /home/excel/downloads/urbit/urb/urbit.pill
Aborted (core dumped)
Any help would be appreciated.
Thank you,
Andrew
--
You received this message because you are subscribed to the Google
Groups
Post by Andrew D'Angelo
"urbit" group.
To unsubscribe from this group and stop receiving emails from it, send
an
<javascript:>.
Post by Andrew D'Angelo
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
2016-02-15 22:16:50 UTC
Permalink
Wow, that's quite unusual -- it would seem to indicate a busted pill
somehow. If you rebuild with DEBUG=no, does it go back to crashing?
Post by Andrew D'Angelo
Rebuilding urbit with "DEBUG=yes" stops the crash, strangely enough.
Reading symbols from /home/excel/downloads/urbit/bin/urbit...done.
[New LWP 24876]
warning: Can't read pathname for load map: Input/output error.
[Thread debugging using libthread_db enabled]
Using host libthread_db library
"/lib/i386-linux-gnu/i686/cmov/libthread_db.so.1".
Core was generated by `bin/urbit -c mycomet'.
Program terminated with signal 6, Aborted.
#0 0xb776d424 in __kernel_vsyscall ()
(gdb) bt
#0 0xb776d424 in __kernel_vsyscall ()
#1 0xb71d6661 in *__GI_raise (sig=6)
at ../nptl/sysdeps/unix/sysv/linux/raise.c:64
#2 0xb71d9a92 in *__GI_abort ()
at abort.c:92
#3 0x0805deea in u3m_bail ()
#4 0x0806fb19 in _cue_in ()
#5 0x0806fc67 in u3ke_cue ()
#6 0x080647a3 in u3v_make ()
#7 0x0805fd06 in u3m_boot ()
#8 0x0804ed46 in main ()
Post by Curtis Yarvin
Sorry, Andrew! Any chance you can produce a stack trace on that
coredump? gdb bin/urbit core should do it, then 'bt' from the gdb
command line. For extra points, change DEBUG=no to DEBUG=yes in
Makefile.
Also, in case you somehow installed a very old version, try `rm -rf
mycomet` first.
Post by Andrew D'Angelo
Hello,
I'm trying to get started with urbit on Debian Wheezy.
I've tried both installing urbit from the unofficial Debian package and
building from source, both running in a PuTTY session and a forwarded xterm
session. Every time I try bin/urbit -c mycomet I get
~
urbit: home is mycomet
loom: mapped 2048MB
boot: installed 229 jets
boot: loading /home/excel/downloads/urbit/urb/urbit.pill
Aborted (core dumped)
Any help would be appreciated.
Thank you,
Andrew
--
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
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.
Andrew D'Angelo
2016-02-15 22:18:11 UTC
Permalink
Yes, a fresh build with "DEBUG=no" crashes every time.
Post by Curtis Yarvin
Wow, that's quite unusual -- it would seem to indicate a busted pill
somehow. If you rebuild with DEBUG=no, does it go back to crashing?
Post by Andrew D'Angelo
Rebuilding urbit with "DEBUG=yes" stops the crash, strangely enough.
Reading symbols from /home/excel/downloads/urbit/bin/urbit...done.
[New LWP 24876]
warning: Can't read pathname for load map: Input/output error.
[Thread debugging using libthread_db enabled]
Using host libthread_db library
"/lib/i386-linux-gnu/i686/cmov/libthread_db.so.1".
Core was generated by `bin/urbit -c mycomet'.
Program terminated with signal 6, Aborted.
#0 0xb776d424 in __kernel_vsyscall ()
(gdb) bt
#0 0xb776d424 in __kernel_vsyscall ()
#1 0xb71d6661 in *__GI_raise (sig=6)
at ../nptl/sysdeps/unix/sysv/linux/raise.c:64
#2 0xb71d9a92 in *__GI_abort ()
at abort.c:92
#3 0x0805deea in u3m_bail ()
#4 0x0806fb19 in _cue_in ()
#5 0x0806fc67 in u3ke_cue ()
#6 0x080647a3 in u3v_make ()
#7 0x0805fd06 in u3m_boot ()
#8 0x0804ed46 in main ()
Post by Curtis Yarvin
Sorry, Andrew! Any chance you can produce a stack trace on that
coredump? gdb bin/urbit core should do it, then 'bt' from the gdb
command line. For extra points, change DEBUG=no to DEBUG=yes in
Makefile.
Also, in case you somehow installed a very old version, try `rm -rf
mycomet` first.
Post by Andrew D'Angelo
Hello,
I'm trying to get started with urbit on Debian Wheezy.
I've tried both installing urbit from the unofficial Debian package
and
Post by Andrew D'Angelo
Post by Curtis Yarvin
Post by Andrew D'Angelo
building from source, both running in a PuTTY session and a forwarded xterm
session. Every time I try bin/urbit -c mycomet I get
~
urbit: home is mycomet
loom: mapped 2048MB
boot: installed 229 jets
boot: loading /home/excel/downloads/urbit/urb/urbit.pill
Aborted (core dumped)
Any help would be appreciated.
Thank you,
Andrew
--
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
Post by Andrew D'Angelo
Post by Curtis Yarvin
Post by Andrew D'Angelo
an
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google
Groups
Post by Andrew D'Angelo
"urbit" group.
To unsubscribe from this group and stop receiving emails from it, send
an
<javascript:>.
Post by Andrew D'Angelo
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
2016-02-15 22:35:05 UTC
Permalink
Bizarre. Can we get an md5 urb/urbit.pill?

We're in the middle of a large repo revision, so I hope something
hasn't become corrupted here... Raymond?
Post by Andrew D'Angelo
Yes, a fresh build with "DEBUG=no" crashes every time.
Post by Curtis Yarvin
Wow, that's quite unusual -- it would seem to indicate a busted pill
somehow. If you rebuild with DEBUG=no, does it go back to crashing?
Post by Andrew D'Angelo
Rebuilding urbit with "DEBUG=yes" stops the crash, strangely enough.
Reading symbols from /home/excel/downloads/urbit/bin/urbit...done.
[New LWP 24876]
warning: Can't read pathname for load map: Input/output error.
[Thread debugging using libthread_db enabled]
Using host libthread_db library
"/lib/i386-linux-gnu/i686/cmov/libthread_db.so.1".
Core was generated by `bin/urbit -c mycomet'.
Program terminated with signal 6, Aborted.
#0 0xb776d424 in __kernel_vsyscall ()
(gdb) bt
#0 0xb776d424 in __kernel_vsyscall ()
#1 0xb71d6661 in *__GI_raise (sig=6)
at ../nptl/sysdeps/unix/sysv/linux/raise.c:64
#2 0xb71d9a92 in *__GI_abort ()
at abort.c:92
#3 0x0805deea in u3m_bail ()
#4 0x0806fb19 in _cue_in ()
#5 0x0806fc67 in u3ke_cue ()
#6 0x080647a3 in u3v_make ()
#7 0x0805fd06 in u3m_boot ()
#8 0x0804ed46 in main ()
Post by Curtis Yarvin
Sorry, Andrew! Any chance you can produce a stack trace on that
coredump? gdb bin/urbit core should do it, then 'bt' from the gdb
command line. For extra points, change DEBUG=no to DEBUG=yes in
Makefile.
Also, in case you somehow installed a very old version, try `rm -rf
mycomet` first.
Post by Andrew D'Angelo
Hello,
I'm trying to get started with urbit on Debian Wheezy.
I've tried both installing urbit from the unofficial Debian package and
building from source, both running in a PuTTY session and a forwarded xterm
session. Every time I try bin/urbit -c mycomet I get
~
urbit: home is mycomet
loom: mapped 2048MB
boot: installed 229 jets
boot: loading /home/excel/downloads/urbit/urb/urbit.pill
Aborted (core dumped)
Any help would be appreciated.
Thank you,
Andrew
--
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
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
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.
Andrew D'Angelo
2016-02-15 22:44:00 UTC
Permalink
getting

6ff2d2c635769bff97d5e18d4e4c66dd urb/urbit.pill
--
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
2016-02-15 23:03:06 UTC
Permalink
I did have intermittent problems with that one. When we breach (hopefully in
the next few minutes), there won't be a pill that straddles a big version
boundary, and that version's much better tested.

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.
Andrew D'Angelo
2016-02-15 22:53:00 UTC
Permalink
To clarify: getting a hash of 6ff2d2c635769bff97d5e18d4e4c66dd for both
"DEBUG=no" and "DEBUG=yes".
--
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
2016-02-15 23:20:30 UTC
Permalink
Let me see if Ray has an opinion. He may also have a wheezy test box...

Sent from my iPhone
To clarify: getting a hash of 6ff2d2c635769bff97d5e18d4e4c66dd for both "DEBUG=no" and "DEBUG=yes".
--
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.
Loading...