Eliminate the 'no debug symbols in executable' warning on mac #3495

brson · 2012-09-14T05:26:28Z

Perhaps there's a minimum amount of debug info we can output by default without breaking things. This is alarming to newcomers.

jdm · 2012-09-15T01:31:18Z

I am 99% confident this comes straight from dsymutil.

brson · 2012-11-01T18:17:01Z

Possibly related to #3899

graydon · 2013-03-20T20:06:41Z

non-critical for 0.6, de-milestoning

ryanseys · 2013-04-04T03:58:52Z

+1 to fix this or provide temporary "fix"

Mr0grog · 2013-04-15T18:58:47Z

As a new user curious about the language, this definitely made me think I'd done something wrong while building. This issue is also not a top result in Google if you search for the full error message and I haven't seen anywhere else that the issue is detailed.

While this is totally understandable in a pre 1.0 release, it would be really nice to have a note that it's expected in the README and/or printed to the console at the end of the build output.

carter-thaxton · 2013-04-16T16:25:57Z

+1
30 seconds into playing with rust, initial impression: 0.6 is still not ready for anything more than casual experimentation.
If that's the message you intend to send, well done!

rroels · 2013-04-30T14:27:08Z

+1

Occurs when building rust, and when compiling .rs files. I was almost certain my build had failed since the last ~6 lines were these warnings (while everything was fine). I also get this warning every time I compile any .rs file.

brson · 2013-04-30T20:47:09Z

Nominating, production ready.

graydon · 2013-05-09T20:08:40Z

accepted for production-ready milestone

Mr0grog · 2013-05-13T00:19:31Z

Thanks! I know it's a small thing, but I certainly appreciate it :)

jdm · 2013-05-13T02:10:24Z

I'd be curious what happens if we stop running dsymutil for non-debug builds. In particular, does the gdb experience suffer at all when debugging the resulting binary?

cadencemarseille · 2013-10-06T14:19:10Z

I am writing a rustpkg script for rust-pcre to fix cadencemarseille/rust-pcre#1 and this is tripping me up because part of the script looks at rust run output, which includes this warning in the ProcessOutput.output data.

For now I think I'll just use the last line of output, but it would be great to have this issue fixed.

mcandre · 2014-01-13T23:10:56Z

I'm still getting this in Homebrew Rust on Mavericks.

Trace:

$ cat hello.rs 
extern mod std;

use std::io::println;

fn main() {
  println("Hello World!");
}

$ rustc hello.rs 
warning: no debug symbols in executable (-arch x86_64)

$ ./hello
Hello World!

System:

$ rust --version
rust 0.8
host: x86_64-apple-darwin

$ brew --version
0.9.5

$ system_profiler SPSoftwareDataType | grep 'System Version'
      System Version: OS X 10.9.1 (13B42)

When Homebrew gets Rust 0.9 for Mavericks, will this be fixed?

metajack · 2014-01-13T23:21:39Z

I get this all the time still.

jdm · 2014-01-14T06:16:39Z

That's probably because we build servo with debug symbols, hence we run dsymutil. I would expect @mcandre will have a better experience.

keep missed comments appearing after the struct/enum ident

data_race: make the release/acquire API more clear

rust-log-analyzer · 2024-04-20T09:30:20Z

The job x86_64-gnu-tools failed! Check out the build log: (web) (plain)

Click to see the possible cause of the failure (guessed by this bot)


## Running ui tests in tests/panic for x86_64-unknown-linux-gnu
   Compiler: "MIRI_ENV_VAR_TEST"="0" "MIRI_TEMP"="/tmp/miri-uitest-cdqLHa" "RUST_BACKTRACE"="1" /checkout/obj/build/x86_64-unknown-linux-gnu/stage1/bin/miri "--error-format=json" "--sysroot=/checkout/obj/build/x86_64-unknown-linux-gnu/miri-sysroot" "-Dwarnings" "-Dunused" "-Ainternal_features" "-Zui-testing" "--target" "x86_64-unknown-linux-gnu" "--out-dir" OUT_DIR

FAILED TEST: tests/panic/mir-validation.rs
command: MIRI_ENV_VAR_TEST="0" MIRI_TEMP="/tmp/miri-uitest-cdqLHa" RUST_BACKTRACE="1" "/checkout/obj/build/x86_64-unknown-linux-gnu/stage1/bin/miri" "--error-format=json" "--sysroot=/checkout/obj/build/x86_64-unknown-linux-gnu/miri-sysroot" "-Dwarnings" "-Dunused" "-Ainternal_features" "-Zui-testing" "--target" "x86_64-unknown-linux-gnu" "--extern" "getrandom_01=/checkout/obj/build/x86_64-unknown-linux-gnu/stage1-tools/ui/miri/x86_64-unknown-linux-gnu/debug/deps/libgetrandom-92193960c42a79dc.rlib" "--extern" "getrandom_01=/checkout/obj/build/x86_64-unknown-linux-gnu/stage1-tools/ui/miri/x86_64-unknown-linux-gnu/debug/deps/libgetrandom-92193960c42a79dc.rmeta" "--extern" "getrandom_02=/checkout/obj/build/x86_64-unknown-linux-gnu/stage1-tools/ui/miri/x86_64-unknown-linux-gnu/debug/deps/libgetrandom-6943689c36c748b2.rlib" "--extern" "getrandom_02=/checkout/obj/build/x86_64-unknown-linux-gnu/stage1-tools/ui/miri/x86_64-unknown-linux-gnu/debug/deps/libgetrandom-6943689c36c748b2.rmeta" "--extern" "libc=/checkout/obj/build/x86_64-unknown-linux-gnu/stage1-tools/ui/miri/x86_64-unknown-linux-gnu/debug/deps/liblibc-6a1f771c5476c94d.rlib" "--extern" "libc=/checkout/obj/build/x86_64-unknown-linux-gnu/stage1-tools/ui/miri/x86_64-unknown-linux-gnu/debug/deps/liblibc-6a1f771c5476c94d.rmeta" "--extern" "num_cpus=/checkout/obj/build/x86_64-unknown-linux-gnu/stage1-tools/ui/miri/x86_64-unknown-linux-gnu/debug/deps/libnum_cpus-bf15ee602c622fe7.rlib" "--extern" "num_cpus=/checkout/obj/build/x86_64-unknown-linux-gnu/stage1-tools/ui/miri/x86_64-unknown-linux-gnu/debug/deps/libnum_cpus-bf15ee602c622fe7.rmeta" "--extern" "rand=/checkout/obj/build/x86_64-unknown-linux-gnu/stage1-tools/ui/miri/x86_64-unknown-linux-gnu/debug/deps/librand-99beb3b1b6cc771a.rlib" "--extern" "rand=/checkout/obj/build/x86_64-unknown-linux-gnu/stage1-tools/ui/miri/x86_64-unknown-linux-gnu/debug/deps/librand-99beb3b1b6cc771a.rmeta" "--extern" "tempfile=/checkout/obj/build/x86_64-unknown-linux-gnu/stage1-tools/ui/miri/x86_64-unknown-linux-gnu/debug/deps/libtempfile-c797246b1763c35c.rlib" "--extern" "tempfile=/checkout/obj/build/x86_64-unknown-linux-gnu/stage1-tools/ui/miri/x86_64-unknown-linux-gnu/debug/deps/libtempfile-c797246b1763c35c.rmeta" "--extern" "page_size=/checkout/obj/build/x86_64-unknown-linux-gnu/stage1-tools/ui/miri/x86_64-unknown-linux-gnu/debug/deps/libpage_size-8928013056a2112d.rlib" "--extern" "page_size=/checkout/obj/build/x86_64-unknown-linux-gnu/stage1-tools/ui/miri/x86_64-unknown-linux-gnu/debug/deps/libpage_size-8928013056a2112d.rmeta" "--extern" "tokio=/checkout/obj/build/x86_64-unknown-linux-gnu/stage1-tools/ui/miri/x86_64-unknown-linux-gnu/debug/deps/libtokio-820b2a7a0f0dfcbf.rlib" "--extern" "tokio=/checkout/obj/build/x86_64-unknown-linux-gnu/stage1-tools/ui/miri/x86_64-unknown-linux-gnu/debug/deps/libtokio-820b2a7a0f0dfcbf.rmeta" "-L" "/checkout/obj/build/x86_64-unknown-linux-gnu/stage1-tools/ui/miri/x86_64-unknown-linux-gnu/debug/deps" "-L" "/checkout/obj/build/x86_64-unknown-linux-gnu/stage1-tools/ui/miri/debug/deps" "--out-dir" "/checkout/obj/build/x86_64-unknown-linux-gnu/stage1-tools/ui/tests/panic" "tests/panic/mir-validation.rs" "--edition" "2021"
error: actual output differed from expected
error: actual output differed from expected
Execute `./miri test --bless` to update `tests/panic/mir-validation.stderr` to the actual output
--- tests/panic/mir-validation.stderr
 thread 'rustc' panicked at compiler/rustc_const_eval/src/transform/validate.rs:LL:CC:
 thread 'rustc' panicked at compiler/rustc_const_eval/src/transform/validate.rs:LL:CC:
 broken MIR in Item(DefId) (after phase change to runtime-optimized) at bb0[1]:
 
 
 
+warning: the ICE couldn't be written to `/checkout/src/tools/miri/rustc-ice-2024-04-20T09_30_09-57307.txt`: Read-only file system (os error 30)
 
+
 query stack during panic:
 #0 [optimized_mir] optimizing MIR for `main`
 #0 [optimized_mir] optimizing MIR for `main`
... 7 lines skipped ...
    |
 


full stderr:
thread 'rustc' panicked at compiler/rustc_const_eval/src/transform/validate.rs:89:25:
broken MIR in Item(DefId(0:4 ~ mir_validation[f1b6]::main)) (after phase change to runtime-optimized) at bb0[1]:
(*(_2.0: *mut i32)), has deref at the wrong place
   0: rust_begin_unwind
   1: core::panicking::panic_fmt
   1: core::panicking::panic_fmt
   2: <rustc_const_eval::transform::validate::CfgChecker>::fail::<alloc::string::String>
   3: <rustc_const_eval::transform::validate::Validator as rustc_middle::mir::MirPass>::run_pass
   5: rustc_mir_transform::optimized_mir
   5: rustc_mir_transform::optimized_mir
      [... omitted 2 frames ...]
   6: rustc_middle::query::plumbing::query_get_at::<rustc_query_system::query::caches::DefIdCache<rustc_middle::query::erase::Erased<[u8; 8]>>>
   8: <rustc_const_eval::interpret::eval_context::InterpCx<miri::machine::MiriMachine>>::load_mir
   9: <rustc_const_eval::interpret::eval_context::InterpCx<miri::machine::MiriMachine>>::eval_fn_call
   9: <rustc_const_eval::interpret::eval_context::InterpCx<miri::machine::MiriMachine>>::eval_fn_call
  10: <rustc_const_eval::interpret::eval_context::InterpCx<miri::machine::MiriMachine> as miri::concurrency::thread::EvalContextExt>::run_threads
  12: <rustc_middle::ty::context::GlobalCtxt>::enter::<<miri::MiriCompilerCalls as rustc_driver_impl::Callbacks>::after_analysis::{closure#0}, ()>
  13: <miri::MiriCompilerCalls as rustc_driver_impl::Callbacks>::after_analysis
  14: <rustc_interface::interface::Compiler>::enter::<rustc_driver_impl::run_compiler::{closure#0}::{closure#1}, core::result::Result<core::option::Option<rustc_interface::queries::Linker>, rustc_span::ErrorGuaranteed>>
  15: <scoped_tls::ScopedKey<rustc_span::SessionGlobals>>::set::<rustc_interface::util::run_in_thread_with_globals<rustc_interface::util::run_in_thread_pool_with_globals<rustc_interface::interface::run_compiler<core::result::Result<(), rustc_span::ErrorGuaranteed>, rustc_driver_impl::run_compiler::{closure#0}>::{closure#1}, core::result::Result<(), rustc_span::ErrorGuaranteed>>::{closure#0}, core::result::Result<(), rustc_span::ErrorGuaranteed>>::{closure#0}::{closure#0}::{closure#0}, core::result::Result<(), rustc_span::ErrorGuaranteed>>
  15: <scoped_tls::ScopedKey<rustc_span::SessionGlobals>>::set::<rustc_interface::util::run_in_thread_with_globals<rustc_interface::util::run_in_thread_pool_with_globals<rustc_interface::interface::run_compiler<core::result::Result<(), rustc_span::ErrorGuaranteed>, rustc_driver_impl::run_compiler::{closure#0}>::{closure#1}, core::result::Result<(), rustc_span::ErrorGuaranteed>>::{closure#0}, core::result::Result<(), rustc_span::ErrorGuaranteed>>::{closure#0}::{closure#0}::{closure#0}, core::result::Result<(), rustc_span::ErrorGuaranteed>>
  16: rustc_span::create_session_globals_then::<core::result::Result<(), rustc_span::ErrorGuaranteed>, rustc_interface::util::run_in_thread_with_globals<rustc_interface::util::run_in_thread_pool_with_globals<rustc_interface::interface::run_compiler<core::result::Result<(), rustc_span::ErrorGuaranteed>, rustc_driver_impl::run_compiler::{closure#0}>::{closure#1}, core::result::Result<(), rustc_span::ErrorGuaranteed>>::{closure#0}, core::result::Result<(), rustc_span::ErrorGuaranteed>>::{closure#0}::{closure#0}::{closure#0}>
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.

error: the compiler unexpectedly panicked. this is a bug.

note: using internal features is not supported and expected to cause internal compiler errors when used incorrectly

warning: the ICE couldn't be written to `/checkout/src/tools/miri/rustc-ice-2024-04-20T09_30_09-57307.txt`: Read-only file system (os error 30)
note: rustc 1.79.0-nightly (0afaf0a3c 2024-04-20) running on x86_64-unknown-linux-gnu

note: compiler flags: -Z ui-testing


query stack during panic:
#0 [optimized_mir] optimizing MIR for `main`
end of query stack

Miri caused an ICE during evaluation. Here's the interpreter backtrace at the time of the panic:
note: the place in the program where the ICE was triggered
   |
   |
LL |     extern "rust-call" fn call_once(self, args: Args) -> Self::Output;
   |
   = note: BACKTRACE:
   = note: inside `<fn() as std::ops::FnOnce<()>>::call_once - shim(fn())` at /checkout/library/core/src/ops/function.rs:250:5: 250:71
   = note: inside `std::sys_common::backtrace::__rust_begin_short_backtrace::<fn(), ()>` at /checkout/library/std/src/sys_common/backtrace.rs:155:18: 155:21
   = note: inside `std::sys_common::backtrace::__rust_begin_short_backtrace::<fn(), ()>` at /checkout/library/std/src/sys_common/backtrace.rs:155:18: 155:21
   = note: inside closure at /checkout/library/std/src/rt.rs:159:18: 159:82
   = note: inside `std::ops::function::impls::<impl std::ops::FnOnce<()> for &dyn std::ops::Fn() -> i32 + std::marker::Sync + std::panic::RefUnwindSafe>::call_once` at /checkout/library/core/src/ops/function.rs:284:13: 284:31
   = note: inside `std::panicking::r#try::do_call::<&dyn std::ops::Fn() -> i32 + std::marker::Sync + std::panic::RefUnwindSafe, i32>` at /checkout/library/std/src/panicking.rs:559:40: 559:43
   = note: inside `std::panicking::r#try::<i32, &dyn std::ops::Fn() -> i32 + std::marker::Sync + std::panic::RefUnwindSafe>` at /checkout/library/std/src/panicking.rs:523:19: 523:88
   = note: inside `std::panic::catch_unwind::<&dyn std::ops::Fn() -> i32 + std::marker::Sync + std::panic::RefUnwindSafe, i32>` at /checkout/library/std/src/panic.rs:149:14: 149:33
   = note: inside closure at /checkout/library/std/src/rt.rs:141:48: 141:73
   = note: inside `std::panicking::r#try::do_call::<{closure@std::rt::lang_start_internal::{closure#2}}, isize>` at /checkout/library/std/src/panicking.rs:559:40: 559:43
   = note: inside `std::panicking::r#try::<isize, {closure@std::rt::lang_start_internal::{closure#2}}>` at /checkout/library/std/src/panicking.rs:523:19: 523:88
   = note: inside `std::panic::catch_unwind::<{closure@std::rt::lang_start_internal::{closure#2}}, isize>` at /checkout/library/std/src/panic.rs:149:14: 149:33
   = note: inside `std::rt::lang_start::<()>` at /checkout/library/std/src/rt.rs:158:17: 163:6


full stdout:
---
Error: 
   0: ui tests in tests/panic for x86_64-unknown-linux-gnu failed
   1: tests failed

Backtrace omitted. Run with RUST_BACKTRACE=1 environment variable to display it.
Run with RUST_BACKTRACE=full to include source snippets.
error: test failed, to rerun pass `--test ui`
Caused by:
  process didn't exit successfully: `/checkout/obj/build/x86_64-unknown-linux-gnu/stage1-tools/x86_64-unknown-linux-gnu/release/deps/ui-e0a8031545cb2a0d --quiet` (exit status: 1)
Build completed unsuccessfully in 0:03:23
  local time: Sat Apr 20 09:30:11 UTC 2024

catamorphism mentioned this issue Jun 11, 2013

Don't generate debug symbols by default in OSX #7068

Closed

metajack mentioned this issue Aug 17, 2013

Fresh build on OS X Mountain Lion yields "warning: no debug symbols in executable (-arch x86_64)" on compiles #8571

Closed

alexcrichton mentioned this issue Oct 31, 2013

Run dsymutil less on OSX #10198

Merged

bors closed this as completed in 3403503 Nov 12, 2013

bors pushed a commit to rust-lang-ci/rust that referenced this issue May 15, 2021

Merge pull request rust-lang#3495 from scampi/issue-1096

378b28b

keep missed comments appearing after the struct/enum ident

RalfJung pushed a commit to RalfJung/rust that referenced this issue Apr 20, 2024

Auto merge of rust-lang#3495 - RalfJung:data-race-clocks, r=RalfJung

6b0ce8b

data_race: make the release/acquire API more clear

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Eliminate the 'no debug symbols in executable' warning on mac #3495

Eliminate the 'no debug symbols in executable' warning on mac #3495

brson commented Sep 14, 2012

jdm commented Sep 15, 2012

brson commented Nov 1, 2012

graydon commented Mar 20, 2013

ryanseys commented Apr 4, 2013

Mr0grog commented Apr 15, 2013

carter-thaxton commented Apr 16, 2013

rroels commented Apr 30, 2013

brson commented Apr 30, 2013

graydon commented May 9, 2013

Mr0grog commented May 13, 2013

jdm commented May 13, 2013

cadencemarseille commented Oct 6, 2013

mcandre commented Jan 13, 2014

metajack commented Jan 13, 2014

jdm commented Jan 14, 2014

rust-log-analyzer commented Apr 20, 2024

Eliminate the 'no debug symbols in executable' warning on mac #3495

Eliminate the 'no debug symbols in executable' warning on mac #3495

Comments

brson commented Sep 14, 2012

jdm commented Sep 15, 2012

brson commented Nov 1, 2012

graydon commented Mar 20, 2013

ryanseys commented Apr 4, 2013

Mr0grog commented Apr 15, 2013

carter-thaxton commented Apr 16, 2013

rroels commented Apr 30, 2013

brson commented Apr 30, 2013

graydon commented May 9, 2013

Mr0grog commented May 13, 2013

jdm commented May 13, 2013

cadencemarseille commented Oct 6, 2013

mcandre commented Jan 13, 2014

metajack commented Jan 13, 2014

jdm commented Jan 14, 2014

rust-log-analyzer commented Apr 20, 2024