From: Iain Buclaw <ibuclaw@gdcproject.org>
To: Tom Tromey <tromey@redhat.com>
Cc: Pierre Muller <pierre.muller@ics-cnrs.unistra.fr>,
gdb-patches@sourceware.org
Subject: Re: [PATCH] Add d_main_name to dlang.c
Date: Tue, 07 Jan 2014 09:53:00 -0000 [thread overview]
Message-ID: <CABOHX+dV-AQ4SEwywv=OU2Wit62yYLz9BKMs4KcqBT=JNYGdtQ@mail.gmail.com> (raw)
In-Reply-To: <CABOHX+eCMf9_++hn7pkXnD4ta35m-yOR=gAeRexPVtA-A00nTg@mail.gmail.com>
On 3 January 2014 18:18, Iain Buclaw <ibuclaw@gdcproject.org> wrote:
> On 19 November 2013 21:03, Tom Tromey <tromey@redhat.com> wrote:
>> Pierre> I thought that in general, using the mangled name
>> Pierre> would allow to find main even if you do not generate
>> Pierre> any debug information, as long as you do not remove the
>> Pierre> assembler symbols from the executable.
>> Pierre> This seems like a valid reason to prefer mangled name
>> Pierre> over demangled, no?
>>
>> The demangled name ends up in the minimal symbol table as well.
>> It's convoluted but it ends up in symbol_find_demangled_name, which has
>> a case for language_d.
>>
>> Tom
>
> Hi Tom,
>
> (I've just realised that I my last reply was not cc'd into gdb-patches)
>
> The assignments should now be processed.
>
> Since November, I've made a few more changes that are reflected in
> this new patch.
>
> I would add some more tests for D, but I feel that should write a
> complete parser for D expressions first (d-exp.y) - this will be done
> at a later date.
>
By the way, would it be best to split this up into smaller changes?
Regards
Iain.
next prev parent reply other threads:[~2014-01-07 9:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-19 1:53 Iain Buclaw
2013-11-19 16:09 ` Tom Tromey
2013-11-19 17:50 ` Iain Buclaw
2013-11-19 18:06 ` Tom Tromey
2013-11-19 21:05 ` Pierre Muller
[not found] ` <39451.43601527$1384894769@news.gmane.org>
2013-11-19 21:08 ` Tom Tromey
2014-01-03 18:18 ` Iain Buclaw
2014-01-07 9:53 ` Iain Buclaw [this message]
2014-01-07 10:44 ` Joel Brobecker
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='CABOHX+dV-AQ4SEwywv=OU2Wit62yYLz9BKMs4KcqBT=JNYGdtQ@mail.gmail.com' \
--to=ibuclaw@gdcproject.org \
--cc=gdb-patches@sourceware.org \
--cc=pierre.muller@ics-cnrs.unistra.fr \
--cc=tromey@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