Jim,

Are you by any chance using the $optimize compiler directive in your
programs?  I seem to remember reading somewhere that symbolic debugging is
not compatible with code optimization and thus not to specify both
$symdebug and $optimize.

Regards
Paul Christidis



HP-3000 Systems Discussion <[log in to unmask]> wrote on 06/03/2005
05:22:28 AM:

> I did a
>
> :SETDUMP
>
> Before I ran the debugger and I didn't get a stacktrace - just the error
> message. I also ran:
>
> :XDB XDB.PUB.SYS
>
> Of course, it gave me the warning that XDBEND.LIB.SYS was not linked
with
> the program and it displayed symbolic code. However, when I issued the
"S"
> comand to start the debugging session, I got the same "bus error signal"
> error.
>
> When I run my program without the debugger, it runs fine. I wanted to
use
> the debugger to step through my code to make sure it's returning the
data
> I'm looking for.
>
> The problem is that I'm getting the "bus error signal" error on *any*
> program that I run through the debugger. Even generic MANMAN code that I
> never modified.
>
> Jim.
>
> Date:    Fri, 3 Jun 2005 08:09:15 +1000
> From:    john pitman <[log in to unmask]>
> Subject: FW: [HP3000-L] HP Symbolic Debugger - bus error signal
>
> Do a=20
> :setdump
>
> before you run the debugger. It should give a stacktrace of the error =
> when
> it occurs and localize the routine and offset of the problem. The term =
> 'bus
> error' sounds more like a ux msg, and IIRC means a bad address was =
> trying to
> be resolved.
>
> What do you get just running the program by itself? Obviously you =
> wouldn't
> be trying to debug it if it didn't have a problem. Does it get past its
=
> own
> startup code and start doing some work?=20
> Try=20
> Xdb xdb.pub.sys
> And see if it shows you undebugged code of xdb?
>
> jp
>
> -----Original Message-----
> From: HP-3000 Systems Discussion [mailto:[log in to unmask]] On =
> Behalf
> Of James English
> Sent: Friday, 3 June 2005 5:36 AM
> To: [log in to unmask]
> Subject: [HP3000-L] HP Symbolic Debugger - bus error signal
>
> I'm running on an SERIES e3000/N4000-100-33 running MPE/iX version =
> C.70.01
> and I'm using the HP symbolic debugger (Version A.05.06) to debug a =
> FORTRAN
> 77 program. We have MANMAN version 9.1 installed.
>
> I start the debugger like this:
>
> :XDB UT050.FPUB.ACCOUNT
>
> And type "s" to start the debugging session. As soon as I do that I get
=
> the
> error:
>
> xdb: bus error signal; please try a different command.
>
> It wouldn't be too bad if I got the error on just this one program. =
> However,
> I tried this with several different programs and I got the same error.
>  =20
>
> ---------------------------------
> James English
> Financial Systems Analyst
> MIS Department
> TB Wood's Incorporated
> 440 N Fifth Avenue
> Chambersburg, PA 17201
> Phone: (717) 264-7161 x2119
> Fax: (717) 264-0890
> [log in to unmask]
> http://www.tbwoods.com
> ---------------------------------
>
>
> This e-mail is intended solely for the person or entity to which it
> is addressed and may contain confidential and/or privileged
> information. Any review, dissemination, copying, printing,
> forwarding or other use of this e-mail by persons or entities other
> than the addressee is prohibited. If you have received this e-mail
> in error, please contact the sender immediately and delete the
> material from your computer. Opinions, conclusions and other
> information in this message that do not relate to the official
> business of TB Woods Incorporated shall be understood as neither
> given or endorsed by it.
>
> * To join/leave the list, search archives, change list settings, *
> * etc., please visit http://raven.utc.edu/archives/hp3000-l.html *

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *