Hi Randy, For dbx try using the -I option (repeatedly) for source directories and a full path specification for dxexec e.g. dbx -I /usr/local/src/dx-4.0.6/src/exec/dxmods \ -I /usr/local/src/dx-4.0.6/src/exec/dxexec ... \ /usr/local/src/dx-4.0.6/src/exec/dxexec/dxexec
Thanks for any insight your investigations can provide. Pete Randy Polson wrote: > Hi Pete- > Sorry to drop out for a while. I've been stealing time from other things > to work with dx. It was no longer possible to avoid working on the things > for which I am paid. > > Unless you have found the problem, I need some more instructions to work > with a debugger. I tried the steps > below with dbx and xldb. I ended up with two processing running. I tried > dbx -a to connect to a running process, but it gave me errors of not > finding the object code. > > Thanks for your time and patience as I work through my ignorance. > > -Randy > > > Please if you can, do a clean (-g debuggable) build, and perhaps do some > > troubleshooting, briefly: > > > > setenv DXROOT /usr/local/dx (you may need to set DXDATA, DXMACROS > > too) > > dx -edit -uionly & > > cd /usr/local/src/dx/src/exec/dxexec > > (gdb | dbx | xldb) dxexec > > (the mechanisms for passing -r -B arguments to dxexec vary. for xldb > > they > > go on the command line after dxexec, for gdb and dbx it is run -r -B ). > > > > in ui, connect to running server, do your tests, report stack traces (e.g. > > where) etc.
