Watch, Follow, &
Connect with Us

For forums, blogs and more please visit our
Developer Tools Community.


Welcome, Guest
Guest Settings
Help

Thread: Seattle - Windows 10 - debugger does not work


This question is not answered. Helpful answers available: 2. Correct answers available: 1.


Permlink Replies: 4 - Last Post: Sep 23, 2016 4:15 PM Last Post By: John Denton
John Denton

Posts: 3
Registered: 1/14/11
Seattle - Windows 10 - debugger does not work  
Click to report abuse...   Click to reply to this thread Reply
  Posted: Sep 23, 2016 7:18 AM
I recently installed Seattle on a new Windows 10 machine (was on Windows 7 which was always OK). Working in Delphi.
When I try to step through my code by pressing f4, initially the recompile box comes up, followed immediately by a dialog which says:

Debugger Assertion Failure "lastErr == WSAEINTR" in ..\win32src\wmcipc.cpp at line 294

this is followed on closure with another dialog:

Fatal error starting debugger kernal 'Invalid debugger request'. Please save your work and restart RAD Studio 10 Seattle.

Tried the suggestion - makes no difference.
I have switched my Windows Firewall off for both private and public - not a situation I want to stay with. The firewall rules include 2 entries for the debugger kernel private and domain appear to be yes/any throughout.

Never had problems before. Any guidance will be appreciated.
Should have mentioned Seattle Pro.

John

Edited by: John Denton on Sep 23, 2016 7:52 AM
Remy Lebeau (Te...


Posts: 9,447
Registered: 12/23/01
Re: Seattle - Windows 10 - debugger does not work [Edit]  
Click to report abuse...   Click to reply to this thread Reply
  Posted: Sep 23, 2016 12:31 PM   in response to: John Denton in response to: John Denton
John wrote:

Debugger Assertion Failure "lastErr == WSAEINTR" in
..\win32src\wmcipc.cpp at line 294

Long standing problem, no solution:

QC #104007: [x64] Debugger Assertion Failure: "lastErr == WSAEINTR"
http://qc.embarcadero.com/wc/qcmain.aspx?d=104007

QP #RSP-13976: Debugger crash with console app in Win64
https://quality.embarcadero.com/browse/RSP-13976

QP #RSP-12208: Debugger Assertion Failure: "lastErr == WSAEINTR" when trying
to debug a Firemonkey app on OS X and Win64
https://quality.embarcadero.com/browse/RSP-12208

Two of those reports have been closed as "Cannot Reproduce", the other one
"Needs Feedback".

--
Remy Lebeau (TeamB)
John Denton

Posts: 3
Registered: 1/14/11
Re: Seattle - Windows 10 - debugger does not work [Edit]  
Click to report abuse...   Click to reply to this thread Reply
  Posted: Sep 23, 2016 12:41 PM   in response to: Remy Lebeau (Te... in response to: Remy Lebeau (Te...
Remy Lebeau (TeamB) wrote:
John wrote:

Debugger Assertion Failure "lastErr == WSAEINTR" in
..\win32src\wmcipc.cpp at line 294

Long standing problem, no solution:

QC #104007: [x64] Debugger Assertion Failure: "lastErr == WSAEINTR"
http://qc.embarcadero.com/wc/qcmain.aspx?d=104007

QP #RSP-13976: Debugger crash with console app in Win64
https://quality.embarcadero.com/browse/RSP-13976

QP #RSP-12208: Debugger Assertion Failure: "lastErr == WSAEINTR" when trying
to debug a Firemonkey app on OS X and Win64
https://quality.embarcadero.com/browse/RSP-12208

Two of those reports have been closed as "Cannot Reproduce", the other one
"Needs Feedback".

--
Remy Lebeau (TeamB)

Hi Remy,
I've been with this package since the first Delphi and I have certainly never seen anything like it! The package without a debugger is a waste of time. Might as well bin it - it certainly does not give me the confidence to invest £1,000 in 10.1.

I have done a reinstall over the original on a clean Windows 10 machine. I have unloaded it all and done a fresh install (shutting down between each stage). Still the same problem

I can reproduce it - unfortunately :-(

J.

Edited by: John Denton on Sep 23, 2016 12:42 PM
Remy Lebeau (Te...


Posts: 9,447
Registered: 12/23/01
Re: Seattle - Windows 10 - debugger does not work [Edit] [Edit]  
Click to report abuse...   Click to reply to this thread Reply
  Posted: Sep 23, 2016 12:51 PM   in response to: John Denton in response to: John Denton
John wrote:

I can reproduce it - unfortunately :-(

All I can say is file another bug report and provide the exact steps needed
to reproduce it.

--
Remy Lebeau (TeamB)
John Denton

Posts: 3
Registered: 1/14/11
Re: Seattle - Windows 10 - debugger does not work [Edit] [Edit]  
Click to report abuse...   Click to reply to this thread Reply
  Posted: Sep 23, 2016 4:15 PM   in response to: Remy Lebeau (Te... in response to: Remy Lebeau (Te...
All I can say is file another bug report and provide the exact steps needed
to reproduce it.
Remy Lebeau (TeamB)

I shall uninstall and reinstall yet again tomorrow.

Have found another problem. Switched to 32 bit. Toolbar 'Structure' reports 'Cannot resolve unit name ..'
and goes on to list all my 'uses' files - Windows; Messages; SysUtils and so on..

Switch back to 64 bit all OK compiles fine. In 32 bit the error box complains about 'HasTerminatingSlash' argument being too long. But the program does not use that function..

J.
Legend
Helpful Answer (5 pts)
Correct Answer (10 pts)

Server Response from: ETNAJIVE02