Thanks to Thomas Leitner <tom_at_finwds01.tu-graz.ac.at> for his quick response:
Original question:
>> This one comes from some people I know who are porting code to an Alpha
>> running DU ..
>>
>> It seems they are having problems with gcc (off the freeware CD) and dbx.
>> dbx seems to cause the Alpha to crash with an illegal op-code.
>>
>> Before I start squirelling through what they're doing, is anyone aware
>> of any hiccups with dbx and gcc on 4.0b? I thought I'd ask first (rather
>> than find out later).
Reply:
>This is a problem of DBX rather than GCC. Just scan the old arcticles
>of this mailing list at http://www.ornl.gov/cts/archives/mailing-lists/
>and I'm sure you'll find the answer how to avoid that.
>
>Another way would be to install the DU 4.0b patch kit #3 as it is
>available on ftp.service.digital.com
I checked the archive, and found this from April:
>My original posting was:
>
>currently we are being tormented by system crashes that are reliably
deducable to the invocation of certain dbx commands (!).
>
>Basically, the crashes occur, when you do a "dbx -pid ...", define a
certain breakpoint, issue "cont" and, when having reached the breakpoint
condition, "S"tep one instruction forward.
>
>When such a crash first occurred, we had a we had a "good" crash with
information in uerf-Log, /var/adm/crash and so on. Later "bad" crashes just
halted the machine.
>
>Anyone having experienced similar problems / able to offer advice?
>
>OS: Digital Unix 4.0B
>HW: AlphaStation 200 4/166
>
>...
>
>I really do have to say that this is a very nimble mailing list, regarding
the number and speed of feedback mails! All unanimously said that there is
a bug in Digital Unix 4.0B, where normal user dbx sessions can hang or
crash the system (bad bug, isn't i
>t?). The workaround is to rebuild the kernel without the KDEBUG option.
>
>
Received on Mon Sep 08 1997 - 08:45:19 NZST