QualityCentral

Public Report

Report From: Delphi-BCB/Debugger/Kernel [ Add a report in this area ]

Report #: 33684

Status: Closed

Assertion failure

Project: Delphi

Build #: 10.0.2288.4245

Version: 10.0

Submitted By: Bart van der Werf

Report Type: Crash / Data loss / Total failure

Date Reported: 9/8/2006 3:52:34 AM

Severity: Extreme corner case

Last Updated: 11/13/2009 7:56:50 PM

Platform: 95, 98, 2000, NT, XP

Internal Tracking #: 273439

Resolution: Duplicate (Resolution Comments)

Resolved in Build: : 14.0.3593.25826

Duplicate of: None

Voting and Rating

Overall Rating: (1 Total Rating)

2.00 out of 5

Total Votes: None

Description

When starting a program i got this assertion failure, not seen before.

bds.exe - bordkb100n.dll

Assertion failute: "(!"SetThreadContext failed")"
in ..\win32src\thread32.cpp at line 396
Continue execution?
Yes/No

Steps to Reproduce:

Started a program using f9

bds.exe - bordkb100n.dll

Assertion failute: "(!"SetThreadContext failed")"
in ..\win32src\thread32.cpp at line 396
Continue execution?
Yes/No

press yes.

stop the program using ctrl+f2

error

ide becomes unrepsonsive after this, unsaved work is lost.

Workarounds

None

Attachment

None

Comments

Bart van der Werf at 9/8/2006 3:54:00 AM -

press yes.

stop the program using ctrl+f2

error

ide becomes unrepsonsive after this, unsaved work is lost.

Sebastian Modersohn at 9/9/2006 6:44:09 AM -

I've added this to the steps; needless to say that I can't reproduce this.

Patrick Kolla at 9/10/2006 9:17:25 AM -

Well, I can confirm that debugging threads quite often leads to the IDE becoming absolutely unresponsive. So SetThreadContext may just be a problem with that code, and the hanging the general random hanging that comes with thread debugging ;)

Sebastian Modersohn at 9/10/2006 4:39:33 PM -

> Well, I can confirm that debugging threads quite often leads to the IDE becoming absolutely unresponsive.

You don't happen to have steps with a simple test-case, do you? Preferably with thrddemo.dpr from Demos\DelphiWin32\VCLWin32\Threads.

Patrick Kolla at 9/11/2006 7:18:28 AM -

I'm sorry, but I don't have one. The thread where I experience this is really huge, and stripping that down to a test case would be quite a lot of work. I'll keep it in mind for a free minute though.

Bart van der Werf at 9/12/2006 9:18:53 AM -

I know this is a long shot, but assertions ussually indicate either a basic flaw in the code or memory corruption.
The first might be simple to fix if it gets reported.
It is probably the second, but i doubt that is an argument not to report something that caused me to lose work ?

Sebastian Modersohn at 9/13/2006 3:58:45 PM -

> but i doubt that is an argument not to report something that caused me to lose work ?

No, by any means. Having reproducible steps is not a precondition for reporting something in QC. But as long as its not reproducible the report probably won't get opened.
Still these reports may come in handy (e.g. if others are experiencing the same issue). Besides, I've seen R&D engineers encouraging people to report stuff that is not easily reproducible.

Bart van der Werf at 9/19/2006 2:13:05 AM -

This seems to be related to DEP

Quality Central

Developer Tools

Database Tools