Re: [lldb-dev] incorrect shared library addresses

2015-10-14 Thread Greg Clayton via lldb-dev
> On Oct 14, 2015, at 4:04 PM, Ryan Brown wrote: > > Well the go linker is actually what generates code from the IR, so it's > always required. And as it stands now you can cross compile from another > platform as long as you don't link with c code. I don't know if they'd want > to change tha

Re: [lldb-dev] incorrect shared library addresses

2015-10-14 Thread Ryan Brown via lldb-dev
Well the go linker is actually what generates code from the IR, so it's always required. And as it stands now you can cross compile from another platform as long as you don't link with c code. I don't know if they'd want to change that by always using the os x linker. I filed a bug for them to add

Re: [lldb-dev] incorrect shared library addresses

2015-10-14 Thread Greg Clayton via lldb-dev
Glad we identified your problem. Can you guys always use the system linker? Any reason to use another linker? If you continue to a custom linker you will want to modify it to set these. If you compile Go programs that run on iOS simulator or iOS you will want to emit a LC_MIN_VERSION_IOS. Greg

Re: [lldb-dev] incorrect shared library addresses

2015-10-14 Thread Ryan Brown via lldb-dev
Yep, it looks like LC_VERSION_MIN_MACOSX is missing. target list shows: target #0: /private/tmp/gopath/bin/wikilinktester ( arch=x86_64-apple-, platform=host ) specifying --arch doesn't seem to work. It still has the modules loaded starting at 0, and target list says: * target #1: /tmp/gopath/bin

Re: [lldb-dev] incorrect shared library addresses

2015-10-14 Thread Greg Clayton via lldb-dev
I am guessing that your binary is missing a LC_VERSION_MIN_XXX load command and so it is being loaded with "-unknown-unknown" as the architecture. This is probably causing LLDB to load the DynamicLoaderStatic as the dynamic loader which just loads all shared libraries as the address that is cont

Re: [lldb-dev] incorrect shared library addresses

2015-10-14 Thread Ryan Brown via lldb-dev
I have the same behavior with the system lldb and the one I build in xcode. My xcode is Version 6.4 (6E35b) I just hit command-b to build, is that what you mean? I don't really know xcode very well. On Tue, Oct 13, 2015 at 10:08 PM Todd Fiala wrote: > > Breakpoint 1: where = wikilinktester`main

Re: [lldb-dev] incorrect shared library addresses

2015-10-13 Thread Todd Fiala via lldb-dev
> Breakpoint 1: where = wikilinktester`main.main + 805 at wikilinktester.go:35, address = 0x2365 The address of the breakpoint is kinda interesting - that seems suspiciously low for an OS X user executable. Which lldb are you using? If you built it, what process did you use to build

[lldb-dev] incorrect shared library addresses

2015-10-13 Thread Ryan Brown via lldb-dev
I'm having a strange issue debugging a go program. I set a breakpoint, and lldb stops at it. However, lldb thinks it's in a different function: (lldb) b wikilinktester.go:35 Breakpoint 1: where = wikilinktester`main.main + 805 at wikilinktester.go:35, address = 0x2365 (lldb) r Process