[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference turris::digital_unix

Title:DIGITAL UNIX(FORMERLY KNOWN AS DEC OSF/1)
Notice:Welcome to the Digital UNIX Conference
Moderator:SMURF::DENHAM
Created:Thu Mar 16 1995
Last Modified:Fri Jun 06 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:10068
Total number of notes:35879

3391.0. "dbx issues "cannot single step thread" message" by TUXEDO::MANNIX () Thu Nov 16 1995 19:23

T.RTitleUserPersonal
Name
DateLines
3391.1make it a show stopper, that will get my attention!QUARRY::petertrigidly defined areas of doubt and uncertaintyThu Nov 16 1995 20:3820
3391.2Im getting this on single threaded codeCYCLIC::TURNERMon Feb 24 1997 15:1720
 Hello,

 I'm seeing this message when trying to debug single threaded code in dbx
version 3.11.10 on UNIX version 4.0A. It is proving to be quite a problem (
I am not in a position to use DECladebug ).

 Is this likely to be down to bad system configuration, or software build
problems.

 Is there anything that I can do to sort this problem out so that I can use
dbx. I am sure that I have previously been able to debug this code ( built
with the same make files ) in dbx. However I am now trying to debug on a
newly configured system ( UNIX installed from scratch to V4.0 then upgraded
to V4.0A ).

 Any clues ?

	Thanks,

		Barrie.
3391.3let me know if this helps...QUARRY::petertrigidly defined areas of doubt and uncertaintyMon Feb 24 1997 18:056
Given the problems you relate, I can't really imagine what is going on
at the moment.  I'd suggest you use dbx with the -noproc switch to 
see if that helps at all.  But if I could get a test case to track down
what is really going on, that would be appreciated.  

PeterT
3391.4SMURF::DENHAMDigital UNIX KernelMon Feb 24 1997 20:152
    I've seen that when the thread you're trying to debug has SIGTRAP
    blocked. Anything to go on there?
3391.5ThanksCYCLIC::TURNERTue Feb 25 1997 07:059
 Thanks for your responses, I'll investigate further. I'm also going to
attempt to try on a different machine, as I seem to be the only person in
my group that is having this problem and it could be currouption in my
code. The funny thing is though I get the same symptom in two different
images ( which is what made me think it may be a UNIX OS setup problem ).

 I'll keep you up to date.

	Barrie.
3391.6Seems to specific to my environmentCYCLIC::TURNERTue Feb 25 1997 08:034
 I have just run the same images in dbx on a machine running UNIX 3.2C +
dbx 3.11.8. I do not get the same problem.

 Barrie.