From: Daniel Drotos <drdani@mazsola.iit.uni-miskolc.hu>
To: gdb@cygnus.com
Subject: native gdb+simulator
Date: Tue, 13 Apr 1999 03:24:00 -0000 [thread overview]
Message-ID: <Pine.SO4.4.00.9904131055330.3707-100000@mazsola> (raw)
In-Reply-To: <199904130703.AAA16348@cygnus.com>
Hi,
Is it possible to include a simultor if gdb is configured for the
host's target?
I mean, for example I config and compile on elf32-i386 (e.g. linux)
and I'd like to use this bfd target to read in the file to be
debugged, but use a (own written) simulator to actually execute the
code.
Is it possible to hack feature like this into the gdb without
introducing a new bfd target?
Daniel
WARNING: multiple messages have this Message-ID
From: Daniel Drotos <drdani@mazsola.iit.uni-miskolc.hu>
To: gdb@cygnus.com
Subject: native gdb+simulator
Date: Tue, 13 Apr 1999 04:41:00 -0000 [thread overview]
Message-ID: <Pine.SO4.4.00.9904131055330.3707-100000@mazsola> (raw)
Message-ID: <19990413044100.O9pa2-aDCPNNSJmF02iy01aI3Rj4sih5U5I3tFPocUo@z> (raw)
In-Reply-To: <199904130703.AAA16348@cygnus.com>
Hi,
Is it possible to include a simultor if gdb is configured for the
host's target?
I mean, for example I config and compile on elf32-i386 (e.g. linux)
and I'd like to use this bfd target to read in the file to be
debugged, but use a (own written) simulator to actually execute the
code.
Is it possible to hack feature like this into the gdb without
introducing a new bfd target?
Daniel
next parent reply other threads:[~1999-04-13 3:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <199904130703.AAA16348@cygnus.com>
1999-04-13 3:24 ` Daniel Drotos [this message]
1999-04-13 4:41 ` Daniel Drotos
[not found] ` <Pine.SO4.4.00.9904131055330.3707-100000.cygnus.gdb@mazsola>
1999-04-13 21:01 ` Andrew Cagney
1999-04-14 1:53 ` Daniel Drotos
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=Pine.SO4.4.00.9904131055330.3707-100000@mazsola \
--to=drdani@mazsola.iit.uni-miskolc.hu \
--cc=gdb@cygnus.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