From: Jim Blandy <jimb@codesourcery.com>
To: "drizzle drizzle" <drizzle76@gmail.com>
Cc: gdb@sourceware.org
Subject: Re: dwarf 2 clarification
Date: Fri, 30 Mar 2007 18:27:00 -0000 [thread overview]
Message-ID: <m3wt0yio3y.fsf@codesourcery.com> (raw)
In-Reply-To: <7326d8e40703291411y423163bay5db65069d3a4e662@mail.gmail.com> (drizzle drizzle's message of "Thu, 29 Mar 2007 17:11:18 -0400")
"drizzle drizzle" <drizzle76@gmail.com> writes:
> I am using a 32 bit compiler to generate debug information. i want
> to retarget this compiler to now emit emit debug information for a 16
> bit architecture. The compiler is already retarget to generate correct
> code for the 16 bit architecture. So the offsets from the stack
> pointer in the assembly code, the sizes of the symbol are all correct
> in terms of the new architectures address size. Now I was wondering
> from a debug information standpoint, is there any extra education that
> the compiler needs ?
This mailing list is for discussion about the GNU debugger, GDB. Are
you using GDB as your debugger?
prev parent reply other threads:[~2007-03-30 18:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-29 21:11 drizzle drizzle
2007-03-30 18:27 ` Jim Blandy [this message]
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=m3wt0yio3y.fsf@codesourcery.com \
--to=jimb@codesourcery.com \
--cc=drizzle76@gmail.com \
--cc=gdb@sourceware.org \
/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