From: Matt Rice <ratmice@gmail.com>
To: Michael Snyder <msnyder@vmware.com>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: disable objective-c stuff when theres no objective-c cu.
Date: Tue, 05 Oct 2010 23:35:00 -0000 [thread overview]
Message-ID: <AANLkTi=sBN9DvBbrFxjmA-U30HhY7+yPmdWU5y1OFoTr@mail.gmail.com> (raw)
In-Reply-To: <4CABB53A.8000101@vmware.com>
On Tue, Oct 5, 2010 at 4:31 PM, Michael Snyder <msnyder@vmware.com> wrote:
> Matt Rice wrote:
>>
>> this makes it so that a flag is set if either an objective-c
>> compilation unit is found,
>> or the user goes 'set language objective-c' in the case where debug
>> symbols are absent.
>>
>> 2010-10-05 Matt Rice <ratmice@gmail.com>
>>
>> * defs.h: Add comment.
>> * dwarf2read.c (set_cu_language): Notice that a language has been
>> seen.
>> * language.c (set_language): Ditto.
>> (mask_for_language, language_has_cu_loaded): New Functions.
>> (set_language_has_cu_loaded): Ditto.
>> * language.h: Declare new functions.
>> * linespec.c (decode_line_1): Don't lookup objective-c methods
>> unless objective-c has been seen.
>
> Hi Matt,
>
> Do you have a copyright assignment?
Yeah, I do
and I should have probably noted that this is a change of behaviour
so its kind of an RFC, and I didn't think about stabs, so w/ this they
probably require 'set language objective-c' 'set language auto' should
restore the old behaviour
waiting on the testsuite to run, but it looks like gdb.objc/nondebug.exp
is going to require 'set language objective-c'.
next prev parent reply other threads:[~2010-10-05 23:35 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-05 22:37 Matt Rice
2010-10-05 23:31 ` Michael Snyder
2010-10-05 23:35 ` Matt Rice [this message]
2010-10-06 2:30 ` Matt Rice
2010-10-06 8:51 ` Jan Kratochvil
2010-10-06 10:03 ` Matt Rice
2010-10-06 13:12 ` Matt Rice
2010-10-06 17:06 ` Joel Brobecker
2010-10-06 17:54 ` Matt Rice
2010-10-17 20:13 ` Jan Kratochvil
2010-10-17 21:57 ` Matt Rice
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='AANLkTi=sBN9DvBbrFxjmA-U30HhY7+yPmdWU5y1OFoTr@mail.gmail.com' \
--to=ratmice@gmail.com \
--cc=gdb-patches@sourceware.org \
--cc=msnyder@vmware.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