Subject: Re: tracking program counter / assembling objdump output
To: None <>
From: Ignatios Souvatzis <>
List: port-m68k
Date: 09/28/2006 12:01:25
On Wed, Sep 27, 2006 at 07:14:52PM -0400, wrote:
> thanks for the tip.  I've been trying ways to get the info via  gdb.
> The executable in question is a.out-sunos-big format, statically  linked.
> It runs on a sun3/80 under NetBSD 3.0, NetBSD 1.5.3, and SunOS  4.1.1.
> With NetBSD 3.0, I can either run it directly, or run it  all-the-way-through 
> under gdb.  But I can't single step through it, or have  it stop at any 
> breakpoints in gdb.  I can set breakpoints which show up  correctly with "info 
> break", but upon "run"ning, it just runs all the way  through.  If I control-c in 
> the middle, it stops and shows me the actual  program counter, and the 
> dissassemble command shows the correct  instructions.  But if I "si" single machine 
> instruction step - it runs all  the way to the end.  Must be something with the 
> executable is not the  default elf format.

Uhm, yes. GDB must have a way to tell the OS to run the program in a
trapping way - apparently the NetBSD gdb doesn't know how to do that for 
a SunOS program. (Always assuming single step does work for your program...
but stepi works on a 3.0 system with a 4.0_BETA kernel.)

You did use "stepi", right? "step" would require that a) the program
is compiled and linked for debugging and b) gdb knows how read that
information for a SunOS/m68k program.