From: "Battig, Caleb" <Caleb.Battig@netapp.com>
To: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Cc: "Lovett, Stuart" <Stuart.Lovett@netapp.com>,
"Peikes, Wendy" <Wendy.Peikes@netapp.com>
Subject: [PING] Added x86_64 stub for debugging embedded systems running on Intel x86_64 processor architecture.
Date: Mon, 12 Oct 2020 17:51:44 +0000 [thread overview]
Message-ID: <BL0PR06MB4418C30AC75999E88C2E2B16E1070@BL0PR06MB4418.namprd06.prod.outlook.com> (raw)
In-Reply-To: <BL0PR06MB4418CCCF8597C622AC200C61E1300@BL0PR06MB4418.namprd06.prod.outlook.com>
[-- Attachment #1: Type: text/plain, Size: 1165 bytes --]
Caleb Battig
Platform Software Engineer
NetApp
724.741.5226 Direct Phone
Caleb.Battig@netapp.com<mailto:Eugene.Novak@netapp.com>
netapp.com<http://www.netapp.com/us/>
[cid:e9c15ec4-d103-4e38-b97d-ec06fdb0ac3a]
________________________________
From: Battig, Caleb
Sent: Thursday, October 1, 2020 10:27 AM
To: gdb-patches@sourceware.org <gdb-patches@sourceware.org>
Cc: Lovett, Stuart <Stuart.Lovett@netapp.com>; Peikes, Wendy <Wendy.Peikes@netapp.com>
Subject: Added x86_64 stub for debugging embedded systems running on Intel x86_64 processor architecture.
For years there has been no gdb stub for use with embedded systems
running Intel 64 bit CPUs. This is no longer the case. The new stub is
based on the old i386-stub, but provides support for 64 bit registers
and 64 bit interrupt descriptor table (IDT) entries.
gdb/stubs/ChangeLog:
* x86_64-stub.c: New file.
Regards,
Caleb Battig
Platform Software Engineer
NetApp
724.741.5226 Direct Phone
Caleb.Battig@netapp.com<mailto:Eugene.Novak@netapp.com>
netapp.com<http://www.netapp.com/us/>
[cid:a768e24b-cca6-4214-b0a7-28b1f0fe33cd]
[-- Attachment #2: Outlook-nneajore.png --]
[-- Type: image/png, Size: 56478 bytes --]
[-- Attachment #3: Outlook-2yi1s1zs.png --]
[-- Type: image/png, Size: 56478 bytes --]
next parent reply other threads:[~2020-10-12 17:51 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <BL0PR06MB4418CCCF8597C622AC200C61E1300@BL0PR06MB4418.namprd06.prod.outlook.com>
2020-10-12 17:51 ` Battig, Caleb [this message]
2020-10-19 14:18 ` [PING][PING] " Battig, Caleb
2020-10-19 14:29 ` Simon Marchi
2020-10-19 14:38 ` Battig, Caleb
2020-10-19 14:43 ` Battig, Caleb
2020-10-19 15:45 ` Simon Marchi
2020-10-19 22:23 ` Battig, Caleb
2020-10-20 13:09 ` Simon Marchi
2020-10-20 16:34 ` Battig, Caleb
2020-10-22 16:34 ` Battig, Caleb
2020-10-23 0:47 ` Simon Marchi
2020-10-28 22:11 ` Battig, Caleb
2020-11-11 16:39 ` Battig, Caleb
2020-11-11 20:54 ` Simon Marchi
2020-11-11 21:58 ` Battig, Caleb
2020-12-14 15:10 ` Simon Marchi
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=BL0PR06MB4418C30AC75999E88C2E2B16E1070@BL0PR06MB4418.namprd06.prod.outlook.com \
--to=caleb.battig@netapp.com \
--cc=Stuart.Lovett@netapp.com \
--cc=Wendy.Peikes@netapp.com \
--cc=gdb-patches@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