Re: [swift-users] About Swift Package Manager and LLDB

2017-11-06 Thread Fadi Botros‬via swift-users
This happens when try to print(self)Processing command: po print(self) HandleCommand, cmd_obj : 'expression' Handl - Pastebin.com | | | | || | | | | | Processing command: po print(self) HandleCommand, cmd_obj : 'expressio... | | | | This happens when

[swift-users] بخصوص: About Swift Package Manager and LLDB

2017-11-06 Thread Fadi Botros‬via swift-users
Also there is some very weird thing happens When I use ^C to stop debuggingthen REPLimport PerfectTemplate There is no error But when use breakpointThe error happens Is there something weird about breakpoints ? Also please note that on macOS when I use SPM to convert project to Xcode project and

[swift-users] بخصوص: About Swift Package Manager and LLDB

2017-11-06 Thread Fadi Botros‬via swift-users
OK You want it locally It is just the PerfectTemplate without ANY CHANGE (Perfect framework by PerfectlySoft) (Also Kitura makes the same problem, but I didn't try to get a full log to see whether the same problem or not) PerfectlySoft/PerfectTemplate | | | | || | | |

[swift-users] بخصوص: بخصوص: About Swift Package Manager and LLDB

2017-11-06 Thread Fadi Botros‬via swift-users
WEIRD WEIRD WEIRDIt seems it is threading issueBecause when I tried to breakpoint on line 71 file main.swift (like you did)It worked perfectlyI even could "frame variable" fully It seems that perfect framework when handle an HTTP request, it makes something in threads, I don't know how to debug

Re: [swift-users] About Swift Package Manager and LLDB

2017-11-06 Thread Fadi Botros‬via swift-users
I think really like I said in the last message, it is a threading issueBecause debugging on Line 71 (which you debugged): It gives that you are on the main thread Thread #1When on line 31 (which I debugged): It gives that you are on Thread #2 (then you can't import any modules, nor print any

Re: [swift-users] About Swift Package Manager and LLDB

2017-11-06 Thread Fadi Botros‬via swift-users
I don't think Perfect has problems because it debugs perfectly on XcodeKitura may have some flaws because on Xcode also causes some issues BUT YOU STILL CAN GET FRAME, ETC.. WHILE NOT HAVING THOSE IN SPM The problem is in SPMJust make the SPM build Swift Packages like Xcode (or equivalent)

[swift-users] بخصوص: About Swift Package Manager and LLDB

2017-11-07 Thread Fadi Botros‬via swift-users
Some information may be leading to resolve of this problem I think "ld" tool does a lot of the trick Notice the difference between the results of the two compilations (Xcode and SPM): Kitura example via Xcode, when invoked "target modules list" on lldb Gets this[ 0]

[swift-users] بخصوص: About Swift Package Manager and LLDB

2017-11-06 Thread Fadi Botros‬via swift-users
Also please notedI think it is a SPM issue not an LLDB oneBecause when compiled on the same mac with Xcode (Swift package manager generate Xcode project), then use xcode-buildLLDB works perfectly in this circumstances I think you should refine the compilation script generated by SPM to generate

[swift-users] About Swift Package Manager and LLDB

2017-11-06 Thread Fadi Botros‬via swift-users
I'm interested in doing Web Application using Swift and promoting this to be a trend someday.But I couldn't find a way to debug web apps without using XcodeThis is irrelevant because web applications are mainly on Linux, so what if we want to do remote debugging ? I tried using the SPM, and

[swift-users] Swift 4.0 bug in concurrent array access

2018-01-08 Thread Fadi Botros‬via swift-users
I'm on macOS Sierra 10.12.6, and using Swift 4.0Tried to access the array concurrently to see whether is it synchronized or no import Foundation let global = DispatchQueue.global() var array: [Int] = [ - Pastebin.com | | | | || | | | | | import Foundation let

Re: [swift-users] Swift 4.0 bug in concurrent array access

2018-01-08 Thread Fadi Botros‬via swift-users
What about double checking? Something like that if counter != 0 { throw exc } counter += 1if counter != 1 { throw exc }counter += 1 I think the performance penalty is just a check and an increment It could be disabled after optimization or in release version to increase performance من: