Watch, Follow, &
Connect with Us
Public Report
Report From: Kylix/Debugger    [ Add a report in this area ]  
Report #:  4040   Status: Open
Unable to debug threads on new glibc-2.3.2-4.80
Project:  Kylix Build #:  4.186
Version:    3.0 Submitted By:   Dalibor Toman
Report Type:  Basic functionality failure Date Reported:  4/7/2003 8:37:53 AM
Severity:    Commonly encountered problem Last Updated: 3/20/2012 2:24:39 AM
Platform:    RedHat Linux Internal Tracking #:   174938
Resolution: None  Resolved in Build: : None
Duplicate of:  None
Voting and Rating
Overall Rating: (3 Total Ratings)
4.33 out of 5
Total Votes: 9
Description
I am usign Kylix3 Pro on RH8.0 with up2date running (glibc-2.3.2-4.80) . After the new glibc library has been published (and installed) the IDE is not able to reach a breakpoint placed into a thread code (Inside Execute).

Once the thread is started the IDE shows a message (exception report) with 'Trap (5)' text included. Then (after accepting the message box) the IDE will hang in most cases. It will not hang if program reset (CtrlF2) is invoked immediately (the exception report suggest to use F7 or F8 to step into the problem code - but it is tha safe way to hang the IDE).

After the glibc was downgraded to the RH8.0 original one the problem disappeared.

Steps to Reproduce:
1) upgrade to the newer glibc
2) load following project into IDE

program Project1;

uses
   Unit1 in 'Unit1.pas';

VAR
   T : Test;
begin
   T := Test.Create(True);
   T.Resume;
   T.WaitFor;
   T.Free;
end.

--------------

unit Unit1;

interface

uses
   Classes;

type
   test = class(TThread)
   private
     { Private declarations }
   protected
     procedure Execute; override;
   end;

implementation
USES
   SysUtils;

procedure test.Execute;
VAR
   I : Integer;
begin
   for i := 1 to 5 do
   begin
     sleep(1000);
     writeln('aaaaaaaa');
   end;
end;

end.


3) place a breakpoint into test.Execute

4) run the project and expect the exception message.
Workarounds
None
Attachment
None
Comments

Martin Forst at 11/16/2003 11:25:04 PM -
Same on Suse Linux 9.0. Kylix Delphi works correctly but Kylic C++ does not call the execute method of the thread. Sometimes - but not always an exception Trap (5) is shown.

Stephan Gammeter at 2/20/2005 11:58:45 AM -
Same on SuSE Linux 9.2, i also get a "Debugger Internal Error XEV-390" from time to time

Server Response from: ETNACODE01