rustc --ls ICE #2771

Closed
jesse99 opened this Issue Jul 1, 2012 · 5 comments

Comments

Projects
None yet
2 participants
@jesse99
Contributor

jesse99 commented Jul 1, 2012

rust --ls is now ICEing on every rust library I have tried it on. This is with rust from June 30 on Mac. For example doing an --ls on the library from https://github.com/jesse99/rust-socket results in:

gnos: rustc --ls bin/libsocket-9e5595de7eda745e-0.1.dylib 
=Crate Attributes (9e5595de7eda745e)=
#[link(name = "socket",
       vers = "0.1",
       uuid = "AF82CEF5-A320-49C0-AE56-43129C5229D5",
       url = "https://github.com/jdm/rust-socket")]
#[comment = "Rust socket library"]
#[license = "MIT"]
#[crate_type = "lib"]


=External Dependencies=
1 core-d27e4777a53c3e50-0.2
2 std-d399da1ab6f5bec0-0.2

=Items=
htons (fn)
SO_SNDBUF (const)
htonl (fn)
SO_REUSEADDR (const)
sendto (fn)
socket_handle::sockfd (public field)
SO_SNDTIMEO (const)
sockaddr_basic (type)
SO_KEEPALIVE (const)
sockaddr4_in (type)
SOCK_STREAM (const)
AI_CANONNAME (const)
setsockopt (fn)
enablesockopt (fn)
ipv6 (enum)
SO_ERROR (const)
ipv4 (enum)
AI_NUMERICSERV (const)
ntohs (fn)
SO_OOBINLINE (const)
ntohl (fn)
sockaddr (type)
sockaddr6_in (type)
getaddrinfo (fn)
socket_handle (class)
socket_handle (fn)
rust: task failed at 'describe_def: item not found (0, 3571)', /Users/jessejones/Source/Third_Party/rust/src/rustc/metadata/decoder.rs:551
error: internal compiler error: unexpected failure
note: the compiler hit an unexpected failure path. this is a bug
note: try running with RUST_LOG=rustc=0,::rt::backtrace to get further details and report the results to github.com/mozilla/rust/issues
rust: task failed at 'explicit failure', /Users/jessejones/Source/Third_Party/rust/src/rustc/driver/rustc.rs:258
rust: domain main @0x7f934a800010 root task failed
rust: task failed at 'killed', /Users/jessejones/Source/Third_Party/rust/src/libcore/task.rs:461

Setting RUST_LOG didn't produce any additional output.

@catamorphism

This comment has been minimized.

Show comment
Hide comment
@catamorphism

catamorphism Jul 1, 2012

Contributor

Just to be clear, your installed rustc was built from git HEAD as of June 30? That surprises me, because this looks like #2192 , which I fixed six days ago.

Contributor

catamorphism commented Jul 1, 2012

Just to be clear, your installed rustc was built from git HEAD as of June 30? That surprises me, because this looks like #2192 , which I fixed six days ago.

@jesse99

This comment has been minimized.

Show comment
Hide comment
@jesse99

jesse99 Jul 1, 2012

Contributor

Yes

Contributor

jesse99 commented Jul 1, 2012

Yes

@ghost ghost assigned catamorphism Jul 1, 2012

@catamorphism

This comment has been minimized.

Show comment
Hide comment
@catamorphism

catamorphism Jul 1, 2012

Contributor

Ok, I'll try to reproduce.

Contributor

catamorphism commented Jul 1, 2012

Ok, I'll try to reproduce.

@catamorphism

This comment has been minimized.

Show comment
Hide comment
@catamorphism

catamorphism Jul 4, 2012

Contributor

Reproduced with 328fd30 -- I'll look into it.

Contributor

catamorphism commented Jul 4, 2012

Reproduced with 328fd30 -- I'll look into it.

@catamorphism

This comment has been minimized.

Show comment
Hide comment
@catamorphism

catamorphism Jul 6, 2012

Contributor

This appears to be because the list-metadata code is trying to print out info about intrinsic::visit_ty, but the right information about it doesn't get serialized. Further research tomorrow.

Contributor

catamorphism commented Jul 6, 2012

This appears to be because the list-metadata code is trying to print out info about intrinsic::visit_ty, but the right information about it doesn't get serialized. Further research tomorrow.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment