public inbox for crossgcc@sourceware.org
 help / color / mirror / Atom feed
From: "Steve deRosier" <sderosier@vari-lite.com>
To: crossgcc <crossgcc@sources.redhat.com>
Subject: crossgcc debug with HP emulator
Date: Fri, 05 Jan 2001 09:38:00 -0000	[thread overview]
Message-ID: <200101051745.LAA14733@ferret.vlint.com> (raw)

I am having problems creating code with my crossgcc that works properly with
the HP emulator that we are using.  We are converting a project from a
Microtec tool chain to the GNU tool chain for a M68x target.  The crossgcc
tools are configured for m68k-coff (hosted on a Sun), and I can successfully
compile, assemble, link and run (not withstanding code bugs) the code on the
emulator plugged into our target system, but can't seem to get the source
code to be displayed in the emulator window when debugging.

Originally we used the
-g    { generate debug info }
-Gf   { generates fully qualified path names for input files }
flags when compiling our code with the MRI compiler.  This allowed us to
automagically display the C and C++ source in the debug window of our
emulator when we were stepping through code.

Now I am using -gstabs flag on the crossgcc (-g would kill our emulator when
loading symbols due to the gdb specific debug info).  I've also tried to use
-gcoff (doesn't help any, and causes a segfault when using objcopy to create
srecords) and other permutations of -g that seem reasonable

While I can get it running on the emulator and even debug (instruction
stepping specifically), trying to step through C/C++ code at the assembly
instruction level is painful.  Is there a flag that I am missing or another
permutation of the -g flag that will allow me to display the C/C++ source in
my debugger? Is there an equivalent flag to the MRI -Gf that we were using
(and I suspect is mostly responsible for our previous ability to display the
C/C++ source)?

I am a relative newbie to using a crossgcc, so I figure that I am missing
something obvious and simple.  I would greatly appreciate any help from
someone who is doing this successfully.

Thanks,
- Steve


--
Steve deRosier
Embedded Software Engineer
Vari-Lite International, Inc.


------
Want more information?  See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/
Want to unsubscribe? Send a note to crossgcc-unsubscribe@sourceware.cygnus.com

WARNING: multiple messages have this Message-ID
From: "Steve deRosier" <sderosier@vari-lite.com>
To: crossgcc <crossgcc@sources.redhat.com>
Subject: crossgcc debug with HP emulator
Date: Sun, 01 Apr 2001 00:00:00 -0000	[thread overview]
Message-ID: <200101051745.LAA14733@ferret.vlint.com> (raw)
Message-ID: <20010401000000.vCF9KungZ4ttix5mTfZbR8FHRoaJi-o7Ies2PxJtnrI@z> (raw)

I am having problems creating code with my crossgcc that works properly with
the HP emulator that we are using.  We are converting a project from a
Microtec tool chain to the GNU tool chain for a M68x target.  The crossgcc
tools are configured for m68k-coff (hosted on a Sun), and I can successfully
compile, assemble, link and run (not withstanding code bugs) the code on the
emulator plugged into our target system, but can't seem to get the source
code to be displayed in the emulator window when debugging.

Originally we used the
-g    { generate debug info }
-Gf   { generates fully qualified path names for input files }
flags when compiling our code with the MRI compiler.  This allowed us to
automagically display the C and C++ source in the debug window of our
emulator when we were stepping through code.

Now I am using -gstabs flag on the crossgcc (-g would kill our emulator when
loading symbols due to the gdb specific debug info).  I've also tried to use
-gcoff (doesn't help any, and causes a segfault when using objcopy to create
srecords) and other permutations of -g that seem reasonable

While I can get it running on the emulator and even debug (instruction
stepping specifically), trying to step through C/C++ code at the assembly
instruction level is painful.  Is there a flag that I am missing or another
permutation of the -g flag that will allow me to display the C/C++ source in
my debugger? Is there an equivalent flag to the MRI -Gf that we were using
(and I suspect is mostly responsible for our previous ability to display the
C/C++ source)?

I am a relative newbie to using a crossgcc, so I figure that I am missing
something obvious and simple.  I would greatly appreciate any help from
someone who is doing this successfully.

Thanks,
- Steve


--
Steve deRosier
Embedded Software Engineer
Vari-Lite International, Inc.


------
Want more information?  See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/
Want to unsubscribe? Send a note to crossgcc-unsubscribe@sourceware.cygnus.com

             reply	other threads:[~2001-01-05  9:38 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-05  9:38 Steve deRosier [this message]
2001-04-01  0:00 ` Steve deRosier
2001-01-06  4:47 John Breen
2001-04-01  0:00 ` John Breen
2001-01-09  5:54 Jepsen Hans Peter
2001-04-01  0:00 ` Jepsen Hans Peter
2001-01-09  7:50 Steve deRosier
2001-04-01  0:00 ` Steve deRosier
2001-01-09 23:23 Jepsen Hans Peter
2001-04-01  0:00 ` Jepsen Hans Peter

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200101051745.LAA14733@ferret.vlint.com \
    --to=sderosier@vari-lite.com \
    --cc=crossgcc@sources.redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).