From: Giah de Barag <gdb@crelg.com>
To: Roland Schwingel <roland.schwingel@onevision.de>
Cc: GDB Patches <gdb-patches@sourceware.org>
Subject: Re: Restored Objective-C language support
Date: Wed, 14 Sep 2016 07:25:00 -0000 [thread overview]
Message-ID: <D6D04F09-543B-4FAE-B6D2-25BD91CFAE41@crelg.com> (raw)
In-Reply-To: <4b0ed430-3c46-340e-5ee9-fce2ff2d5e6d@onevision.de>
> From: Roland Schwingel <roland.schwingel@onevision.de>
> Date: September 14, 2016 at 02:09:21 EDT
>
> Hi Giah!
>
> This is great news! I noticed that recently that it was broken but yet had no time to evaluate this!
>
> Thanks for your work and I honestly hope this could get merged very soon!
You are very welcome. GDB is quick and easy to build (and very easy to use to debug itself). You could apply these patches to the source, make install, and have yourself a better GDB right away. If you need exact recipe, let me know.
> We use ObjC a lot (even on windows and linux) and therefor need GDB for debugging.
Yes, same here. We were happily working on an older GDB and were shocked to find these bugs when we refreshed our software. I am wondering if there is a GDB language maintainer for objective-c.
> Thanks again,
>
> Roland
next prev parent reply other threads:[~2016-09-14 7:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-14 6:09 Roland Schwingel
2016-09-14 7:25 ` Giah de Barag [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-09-13 21:21 Giah de Barag
2016-09-14 22:54 ` Tom Tromey
2016-09-15 0:31 ` Matt Rice
2016-09-15 19:12 ` Giah de Barag
2016-09-16 5:52 ` Giah de Barag
2016-09-27 21:03 ` Giah de Barag
2016-10-12 2:14 ` Tom Tromey
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=D6D04F09-543B-4FAE-B6D2-25BD91CFAE41@crelg.com \
--to=gdb@crelg.com \
--cc=gdb-patches@sourceware.org \
--cc=roland.schwingel@onevision.de \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).