| Title: | Latest kits: GKS V6.x (see 2535.*), GKS V5.3 (see 2480.*) |
| Notice: | Kits: V6.x -> 2535.*; V5.3 -> 2480.* |
| Moderator: | BGSDEV::CROCKER |
| Created: | Mon Feb 03 1986 |
| Last Modified: | Wed May 28 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 2734 |
| Total number of notes: | 9779 |
Hello all, have a customer who complains he cannot debug his GKS programs with ladebug. Could reproduce the problem with the example backgammon.c (which i compiled with -g flag for the debugger). While stepping through the program the debugger does not go beyond the open_workstation call. Stepping in the open_workstation line gives: thread received signal i/o, stopped (Digital UNIX 4.0, GKS 6.4) Any ideas or workaround ? Thenks in advance for help. /Reinhard
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 2725.1 | Can infer some ideas from release note info | SUBPAC::FARICELLI | Fri Feb 21 1997 10:33 | 15 | |
I can't test this, since I have an ancient version of ladebug, but...
Two problems here; both are mentioned in the release notes.
The info is for dbx, but you can infer for decladebug.
1) GKS uses the fork() call. I believe new versions of ladebug
handle programs that fork. You can set the debug variable
$catchforks and make sure you stay in the parent process
(see 'switch'). (This is the part I can't check)
2) The GKS release notes suggest saying "ignore IO" to avoid
catching a signal it needs.
-- John Faricelli
| |||||
| 2725.2 | Thanks, "ignore io'" did the trick | GYPOS3::EIBL | Reinhard Eibl @FKR, DTN 865-4027 | Fri Feb 21 1997 11:38 | 4 |
John, thanks for the hint. (I should have known that) The option "ignore io" did the trick for the ladebug, it works now. /Reinhard | |||||