Skip to content

rustdoc --version panics #20340

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Closed
brson opened this issue Dec 30, 2014 · 2 comments
Closed

rustdoc --version panics #20340

brson opened this issue Dec 30, 2014 · 2 comments
Labels
E-easy Call for participation: Easy difficulty. Experience needed to fix: Not much. Good first issue. I-crash Issue: The compiler crashes (SIGSEGV, SIGABRT, etc). Use I-ICE instead when the compiler panics. T-rustdoc Relevant to the rustdoc team, which will review and decide on the PR/issue.

Comments

@brson
Copy link
Contributor

brson commented Dec 30, 2014 

thread '<unnamed>' panicked at 'No option 'verbose' defined', /home/brian/dev/rust2/src/libgetopts/lib.rs:286
thread '<main>' panicked at 'called `Result::unwrap()` on an `Err` value: ()', /home/brian/dev/rust2/src/libcore/result.rs:746

It's been doing this forever.
@brson brson added T-rustdoc Relevant to the rustdoc team, which will review and decide on the PR/issue. I-crash Issue: The compiler crashes (SIGSEGV, SIGABRT, etc). Use I-ICE instead when the compiler panics. E-easy Call for participation: Easy difficulty. Experience needed to fix: Not much. Good first issue. labels Dec 30, 2014
@brson
Copy link
Contributor Author

brson commented Dec 30, 2014 

thread '<unnamed>' panicked at 'No option 'verbose' defined', /home/brian/dev/rust2/src/libgetopts/lib.rs:286
stack backtrace:
   1:     0x7f520b35fda0 - sys::backtrace::write::h7573bc5da646212ezat
   2:     0x7f520b37fba0 - failure::on_fail::h820f495fd7cf557asrz
   3:     0x7f520b2f5b00 - rt::unwind::begin_unwind_inner::h235e1612586c5a19w5y
   4:     0x7f520b2f6370 - rt::unwind::begin_unwind_fmt::h530121e87b555cdfb3y
   5:     0x7f52074c5270 - Matches::opt_vals::h4dd9249f598f859adPa
   6:     0x7f52074c5770 - Matches::opt_present::h62475234898191315Qa
   7:     0x7f520a9cec40 - version::hd4a1641352dfcccfHcc
   8:     0x7f520b9ad830 - main_args::h74df2535148fded4Obu
   9:     0x7f520b9ad700 - thunk::F.Invoke<A,$u{20}R$GT$::invoke::h15964369035831039695
  10:     0x7f520b9ac500 - rt::unwind::try::try_fn::h1827587574546456317
  11:     0x7f520b3e48c0 - rust_try_inner
  12:     0x7f520b3e48b0 - rust_try
  13:     0x7f520b9ac870 - thunk::F.Invoke<A,$u{20}R$GT$::invoke::h4649510423361328005
  14:     0x7f520b36f520 - sys::thread::thread_start::h9d0b1d2b3381ba14u3v
  15:     0x7f52064500c0 - start_thread
  16:     0x7f520af9aec9 - __clone
  17:                0x0 - <unknown>
thread '<main>' panicked at 'called `Result::unwrap()` on an `Err` value: ()', /home/brian/dev/rust2/src/libcore/result.rs:746
stack backtrace:
   1:     0x7f520b35fda0 - sys::backtrace::write::h7573bc5da646212ezat
   2:     0x7f520b37fba0 - failure::on_fail::h820f495fd7cf557asrz
   3:     0x7f520b2f5b00 - rt::unwind::begin_unwind_inner::h235e1612586c5a19w5y
   4:     0x7f520b2f6370 - rt::unwind::begin_unwind_fmt::h530121e87b555cdfb3y
   5:     0x7f520b37f870 - rust_begin_unwind
   6:     0x7f520b3c7be0 - panicking::panic_fmt::h8dfb1beb747ffed8lxl
   7:     0x7f520b9aaed0 - main::he83326c4d465a87bs7t
   8:     0x7f520b3e48c0 - rust_try_inner
   9:     0x7f520b3e48b0 - rust_try
  10:     0x7f520b3813b0 - rt::lang_start::hd6228bdcc3cebbe2flz
  11:     0x7f520aec1dd0 - __libc_start_main
  12:     0x7f520c0a3750 - <unknown>
  13:                0x0 - <unknown>

Thanks for the reminder @Ms2ger!

@fhahn
Copy link
Contributor

fhahn commented Dec 30, 2014

I'll look into this.

@fhahn fhahn mentioned this issue Dec 30, 2014
Merged
alexcrichton added a commit to alexcrichton/rust that referenced this issue Dec 31, 2014
@alexcrichton
rollup merge of rust-lang#20350: fhahn/issue-20340-rustdoc-version
49f14d3 
Patch for rust-lang#20340. `rustdoc --version` panics because it uses `rustc_driver::version`, which in turn checks the `verbose` flag, which was not defined for rustdoc.  In this patch I have added a verbose flag to rustdoc, because I think it should be useful for other things besides --version.

Another possible fix would be to check if a verbose option was defined in `rustc_driver` or add an extra `version` function for rustdoc.
@bors bors closed this as completed in c11e155 Dec 31, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
E-easy Call for participation: Easy difficulty. Experience needed to fix: Not much. Good first issue. I-crash Issue: The compiler crashes (SIGSEGV, SIGABRT, etc). Use I-ICE instead when the compiler panics. T-rustdoc Relevant to the rustdoc team, which will review and decide on the PR/issue.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@brson @fhahn