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

Closed
brson opened this Issue Sep 14, 2012 · 15 comments

Comments

Projects
None yet
10 participants
@brson
Contributor

brson commented Sep 14, 2012

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

@jdm

This comment has been minimized.

Show comment
Hide comment
@jdm

jdm Sep 15, 2012

Contributor

I am 99% confident this comes straight from dsymutil.

Contributor

jdm commented Sep 15, 2012

I am 99% confident this comes straight from dsymutil.

@brson

This comment has been minimized.

Show comment
Hide comment
@brson

brson Nov 1, 2012

Contributor

Possibly related to #3899

Contributor

brson commented Nov 1, 2012

Possibly related to #3899

@graydon

This comment has been minimized.

Show comment
Hide comment
@graydon

graydon Mar 20, 2013

Contributor

non-critical for 0.6, de-milestoning

Contributor

graydon commented Mar 20, 2013

non-critical for 0.6, de-milestoning

@ryanseys

This comment has been minimized.

Show comment
Hide comment
@ryanseys

ryanseys Apr 4, 2013

+1 to fix this or provide temporary "fix"

ryanseys commented Apr 4, 2013

+1 to fix this or provide temporary "fix"

@Mr0grog

This comment has been minimized.

Show comment
Hide comment
@Mr0grog

Mr0grog Apr 15, 2013

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.

Mr0grog commented Apr 15, 2013

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

This comment has been minimized.

Show comment
Hide comment
@carter-thaxton

carter-thaxton Apr 16, 2013

+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!

+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

This comment has been minimized.

Show comment
Hide comment
@rroels

rroels Apr 30, 2013

+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.

rroels commented Apr 30, 2013

+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

This comment has been minimized.

Show comment
Hide comment
@brson

brson Apr 30, 2013

Contributor

Nominating, production ready.

Contributor

brson commented Apr 30, 2013

Nominating, production ready.

@graydon

This comment has been minimized.

Show comment
Hide comment
@graydon

graydon May 9, 2013

Contributor

accepted for production-ready milestone

Contributor

graydon commented May 9, 2013

accepted for production-ready milestone

@Mr0grog

This comment has been minimized.

Show comment
Hide comment
@Mr0grog

Mr0grog May 13, 2013

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

Mr0grog commented May 13, 2013

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

@jdm

This comment has been minimized.

Show comment
Hide comment
@jdm

jdm May 13, 2013

Contributor

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?

Contributor

jdm commented May 13, 2013

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

This comment has been minimized.

Show comment
Hide comment
@cadencemarseille

cadencemarseille Oct 6, 2013

Contributor

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.

Contributor

cadencemarseille commented Oct 6, 2013

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

This comment has been minimized.

Show comment
Hide comment
@mcandre

mcandre Jan 13, 2014

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?

mcandre commented Jan 13, 2014

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

This comment has been minimized.

Show comment
Hide comment
@metajack

metajack Jan 13, 2014

Contributor

I get this all the time still.

Contributor

metajack commented Jan 13, 2014

I get this all the time still.

@jdm

This comment has been minimized.

Show comment
Hide comment
@jdm

jdm Jan 14, 2014

Contributor

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

Contributor

jdm commented Jan 14, 2014

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

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