From: Cal Erickson <cal_erickson@mvista.com>
To: Serge Nikulin <nikulin@actsw.amat.com>
Cc: insight@sourceware.cygnus.com
Subject: Re: How to embed path info into assembler sources?
Date: Thu, 13 Jul 2000 10:57:00 -0000 [thread overview]
Message-ID: <396E02D0.AAC4D516@mvista.com> (raw)
In-Reply-To: <009301bfecef$ca393970$35758798@mis.amat.com>
Serge,
Actually what is wrong is that the object modules generated
do not have the path information in them for debug information.
If you can re-assemble these modules using the -g option you
should get teh debug information GDB needs. The default is
option is -ng.
Cal Erickson MontaVista Support
Serge Nikulin wrote:
> Hi, All
>
> Among other files my project has many M68K assembler sources in MRI format.
> The problem: GDB can not find these files to show the sources.
> Apparently these assembler files have to contain some path information
> embedded into them.
> Question: What is the right way to embed this info in my *.abs file?
> --target=m68k-coff
> host platform is NT4 + Cygwin
> GDB is in TCP/IP remote mode.
>
> Thank you
> Serge
--
===========================================================================
Cal Erickson MontaVista Software Inc.
Customer Support Engineer 490 Potrero Avenue
Phone (408) 328-0304 Sunnyvale CA 94085
Fax (408) 328-9204 e-mail cal_erickson@mvista.com
Pager 877-566-2012 support 1-800-759-8888 pin 202-7489
web http://www.mvista.com support e-mail: support@mvista.com
eCode: http://cal@work.com.ecode.com
===========================================================================
next prev parent reply other threads:[~2000-07-13 10:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-07-13 10:29 Serge Nikulin
2000-07-13 10:57 ` Cal Erickson [this message]
2000-07-13 11:19 ` Serge Nikulin
[not found] ` <396E156C.A427B893@mvista.com>
2000-07-13 14:38 ` Serge Nikulin
2000-07-14 6:01 ` Keith Seitz
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=396E02D0.AAC4D516@mvista.com \
--to=cal_erickson@mvista.com \
--cc=insight@sourceware.cygnus.com \
--cc=nikulin@actsw.amat.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).