[Bug go/65798] runtime.Caller returns ok=true when return data is invalid

2015-04-17 Thread ian at airs dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65798 Ian Lance Taylor changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|---

[Bug go/65798] runtime.Caller returns ok=true when return data is invalid

2015-04-17 Thread ian at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65798 --- Comment #3 from ian at gcc dot gnu.org --- Author: ian Date: Fri Apr 17 21:58:58 2015 New Revision: 03 URL: https://gcc.gnu.org/viewcvs?rev=03&root=gcc&view=rev Log: PR go/65798 runtime: In Caller don't return ok == true if PC ==

[Bug go/65798] runtime.Caller returns ok=true when return data is invalid

2015-04-17 Thread ian at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65798 --- Comment #4 from ian at gcc dot gnu.org --- Author: ian Date: Fri Apr 17 21:59:10 2015 New Revision: 04 URL: https://gcc.gnu.org/viewcvs?rev=04&root=gcc&view=rev Log: PR go/65798 runtime: In Caller don't return ok == true if PC ==

[Bug go/65798] runtime.Caller returns ok=true when return data is invalid

2015-04-17 Thread ian at airs dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65798 --- Comment #2 from Ian Lance Taylor --- I don't see it as a good idea to ignore an empty file name, but I'm fine with ignoring a 0 PC, so that is what I will implement. Though I am definitely curious how they got a 0 PC from runtime.Caller.

[Bug go/65798] runtime.Caller returns ok=true when return data is invalid

2015-04-17 Thread ian at airs dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65798 --- Comment #1 from Ian Lance Taylor --- The libgo code actually follows the lead of the gc code here. The 1.3 code, in C, said this: } else if((f = runtime·findfunc(rpc[1])) == nil) { retfile = runtime·emptystring; retline