From: David Relson <relson@osagesoftware.com>
To: gdb@sources.redhat.com
Subject: Re: Huge Apple gdb code dropping^H^H^H^H
Date: Thu, 29 Nov 2001 07:29:00 -0000 [thread overview]
Message-ID: <4.3.2.7.2.20011129101820.00b5d730@mail.osagesoftware.com> (raw)
In-Reply-To: <20011129005901.A60085@molenda.com>
At 03:59 AM 11/29/01, Jason Molenda wrote:
>Objective C is a version of C with classes from NeXT. It uses
>brackets a lot, and its programmers think it's a great language. :-)
>Most importantly to gdb, ObjC names have no mangled form and have
>lots of spaces in them - you'll see symbol names like "-[NSExcpetion
>raise]" and that's how it looks at all stages of compilation/reading.
Jason,
This is good news! Objective C is one of the languages supported by
gcc. It is also the language used in the GNUstep project, which brings
NeXTSTEP/OpenStep capability to Linux, BSD, Windoze, etc. Of importance to
me, it allows a project I wrote for NeXTSTEP/OpenStep to run on Linux.
Objective C support has not been part of mainline gdb for several years -
at least since gdb 4.17. There have been "unofficial" patches for 4.17,
4.18, and 5.0, but as gdb has evolved over the years it has become
increasingly difficult to port the unofficial patches to each successive
version of gdb. Having the Objective C support code be part of the
official, mainline of gdb is something I've wanted for the last couple of
years.
David
WARNING: multiple messages have this Message-ID
From: David Relson <relson@osagesoftware.com>
To: gdb@sources.redhat.com
Subject: Re: Huge Apple gdb code dropping^H^H^H^H
Date: Sat, 24 Nov 2001 12:36:00 -0000 [thread overview]
Message-ID: <4.3.2.7.2.20011129101820.00b5d730@mail.osagesoftware.com> (raw)
Message-ID: <20011124123600.rxqwFZUeRaAxRUFWjGo5aYAl0I4kDOSAveOMEEo7vF8@z> (raw)
In-Reply-To: <20011129005901.A60085@molenda.com>
At 03:59 AM 11/29/01, Jason Molenda wrote:
>Objective C is a version of C with classes from NeXT. It uses
>brackets a lot, and its programmers think it's a great language. :-)
>Most importantly to gdb, ObjC names have no mangled form and have
>lots of spaces in them - you'll see symbol names like "-[NSExcpetion
>raise]" and that's how it looks at all stages of compilation/reading.
Jason,
This is good news! Objective C is one of the languages supported by
gcc. It is also the language used in the GNUstep project, which brings
NeXTSTEP/OpenStep capability to Linux, BSD, Windoze, etc. Of importance to
me, it allows a project I wrote for NeXTSTEP/OpenStep to run on Linux.
Objective C support has not been part of mainline gdb for several years -
at least since gdb 4.17. There have been "unofficial" patches for 4.17,
4.18, and 5.0, but as gdb has evolved over the years it has become
increasingly difficult to port the unofficial patches to each successive
version of gdb. Having the Objective C support code be part of the
official, mainline of gdb is something I've wanted for the last couple of
years.
David
next prev parent reply other threads:[~2001-11-29 7:29 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Paul Hilfinger <hilfingr@gnat.com>
2001-11-29 0:59 ` Jason Molenda
2001-11-24 6:24 ` Jason Molenda
2001-11-25 0:39 ` Jason Molenda
2001-11-29 11:12 ` Jason Molenda
2001-11-29 13:34 ` Andrew Cagney
2001-11-25 9:41 ` Andrew Cagney
2001-11-25 9:42 ` Jason Molenda
2001-11-29 13:43 ` Jason Molenda
2001-11-25 9:47 ` Daniel Berlin
2001-11-29 14:15 ` Daniel Berlin
2001-11-29 7:29 ` David Relson [this message]
2001-11-24 12:36 ` David Relson
2001-11-29 10:27 ` Stan Shebs
2001-11-25 0:36 ` Stan Shebs
2001-11-29 11:25 ` Jason Molenda
2001-11-25 1:24 ` Jason Molenda
[not found] ` <200112070641.WAA01521@localhost.localdomain>
2001-12-08 18:05 ` More code code dropping Jason Molenda
[not found] ` <3C10E0F3.2010607@cygnus.com>
2001-12-07 7:43 ` Andrew Cagney
2001-12-08 0:17 ` Paul Hilfinger
2001-12-08 7:56 ` Kevin Buettner
2001-12-08 11:05 ` David Relson
2001-12-08 15:27 ` Andrew Cagney
2001-12-13 5:27 ` Paul N. Hilfinger
2001-12-15 11:32 ` Andrew Cagney
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=4.3.2.7.2.20011129101820.00b5d730@mail.osagesoftware.com \
--to=relson@osagesoftware.com \
--cc=gdb@sources.redhat.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