From: Kai Tietz <Kai.Tietz@onevision.com>
To: Daniel Jacobowitz <drow@false.org>
Cc: gdb@sourceware.org
Subject: Re: Support of gdb for Windows 64 native systems
Date: Thu, 11 Oct 2007 14:18:00 -0000 [thread overview]
Message-ID: <OF210B0721.314AA718-ONC1257371.004E0FFF-C1257371.004E9D77@onevision.de> (raw)
In-Reply-To: <20071011140510.GA17141@caradoc.them.org>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="UTF-8", Size: 1776 bytes --]
Daniel Jacobowitz wrote on 11.10.2007 16:05:10:
> On Thu, Oct 11, 2007 at 03:53:28PM +0200, Kai Tietz wrote:
> > Hello,
> >
> > I want to ask for a volunteer to port gdb for the target
> > x86_64-pc-mingw32. The support is already available in binutils and
gcc,
> > but there is currently no gdb (supporting dwarf2) available for this
host.
> > Is there somebody, who is interested to port it ? Or is willing to
help me
> > to do this port ?
>
> So far there hasn't even been anyone interested in i686-pc-mingw32 for
> the FSF GDB tree; the mingw project has some unsubmitted and
> unassigned patches.
Hmm, wouldn't this be a good chance to bring back the mingw32 support to
the FSF GDB tree ? For sure most of those patches for i?86-mingw are
needed for 64-bit mingw32 too (especially the file-I/O and shared object
stuff). But the calling convention for 64-bit is more simple than for the
32-bit version.
Do you think there is no chance for this support ?
Cheers,
i.A. Kai Tietz
| (\_/) This is Bunny. Copy and paste Bunny
| (='.'=) into your signature to help him gain
| (")_(") world domination.
------------------------------------------------------------------------------------------
OneVision Software Entwicklungs GmbH & Co. KG
Dr.-Leo-Ritter-StraÃe 9 - 93049 Regensburg
Tel: +49.(0)941.78004.0 - Fax: +49.(0)941.78004.489 - www.OneVision.com
Commerzbank Regensburg - BLZ 750 400 62 - Konto 6011050
Handelsregister: HRA 6744, Amtsgericht Regensburg
Komplementärin: OneVision Software Entwicklungs Verwaltungs GmbH
Dr.-Leo-Ritter-StraÃe 9 â 93049 Regensburg
Handelsregister: HRB 8932, Amtsgericht Regensburg - Geschäftsführer:
Ulrike Döhler, Manuela Kluger
\x16º&ÖëzÛ«o|ã¹b²Ö«r\x18\x1d
next prev parent reply other threads:[~2007-10-11 14:18 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-11 13:53 Kai Tietz
2007-10-11 14:05 ` Daniel Jacobowitz
2007-10-11 14:18 ` Kai Tietz [this message]
[not found] <20071011142348.GA18239@caradoc.them.org>
2007-10-11 14:47 ` Kai Tietz
[not found] ` <20071011145549.GA19918@caradoc.them.org>
2007-10-11 16:01 ` Joel Brobecker
2007-10-12 3:38 ` Christopher Faylor
2007-10-12 4:27 ` Joel Brobecker
2007-10-11 16:37 ` Mark Kettenis
2007-10-12 7:19 ` Kai Tietz
2007-10-12 8:44 ` Eli Zaretskii
2007-10-12 16:11 ` Joel Brobecker
2007-10-12 16:51 ` Eli Zaretskii
2007-10-12 17:45 ` Joel Brobecker
2007-10-12 20:29 ` Eli Zaretskii
2007-10-12 22:28 ` Joel Brobecker
2007-10-13 2:41 ` Joel Brobecker
2007-10-13 10:48 ` Eli Zaretskii
2007-10-13 15:47 ` Joel Brobecker
2007-10-13 17:05 ` Christopher Faylor
2007-10-13 17:36 ` Pedro Alves
2007-10-13 19:09 ` Eli Zaretskii
2007-10-13 19:19 ` Pedro Alves
2007-10-13 20:51 ` Joel Brobecker
2007-10-13 22:52 ` Pedro Alves
2007-10-14 5:16 ` Joel Brobecker
2007-10-14 11:44 ` Pedro Alves
2007-10-14 20:33 ` Eli Zaretskii
2007-10-12 17:38 ` Pedro Alves
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=OF210B0721.314AA718-ONC1257371.004E0FFF-C1257371.004E9D77@onevision.de \
--to=kai.tietz@onevision.com \
--cc=drow@false.org \
--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