This is the mail archive of the
mailing list for the GDB project.
Re: [RFA] Fix pascal behavior for class fields
- From: Pedro Alves <palves at redhat dot com>
- To: Pierre Muller <pierre dot muller at ics-cnrs dot unistra dot fr>, "'gdb-patches'" <gdb-patches at sourceware dot org>
- Date: Thu, 08 Jan 2015 13:41:40 +0000
- Subject: Re: [RFA] Fix pascal behavior for class fields
- Authentication-results: sourceware.org; auth=none
- References: <54ae4586 dot 01e3440a dot 7b06 dot fffff844SMTPIN_ADDED_BROKEN at mx dot google dot com> <54AE605A dot 8050308 at redhat dot com> <54ae7f9f dot c323460a dot 36ed dot ffffff30SMTPIN_ADDED_BROKEN at mx dot google dot com>
On 01/08/2015 01:00 PM, Pierre Muller wrote:
>> De : email@example.com [mailto:gdb-patches-
>> firstname.lastname@example.org] De la part de Pedro Alves
>> Envoyé : jeudi 8 janvier 2015 11:48
>> À : Pierre Muller; 'gdb-patches'
>> Objet : Re: [RFA] Fix pascal behavior for class fields
>>> (gdb) p b.x
>>> warning: can't find linker symbol for virtual table for `TA' value
>>> $5 = -1
>>> (gdb) p x
>>> Type TA has no component named x.
>> How about adding this to the test suite?
> The whole testsuite/gpc.pascal is almost empty,
> I never invested time to develop it :(
> At the time I started it, GPC (the GNU pascal compiler)
> was still active, but development apparently
> stopped since quite some time.
> I am unable to install GPC, which means that I cannot test it.
> Would a testsuite that supports only Free Pascal be acceptable?
Do you actually mean, whether it's ok for a new
test (not test suite) to go in untested on GPC? It certainly is.
Better test on FPC than nowhere. :-)
AFAICS, the tests themselves don't really care which compiler
is in use other than for marking xfails; you just call gdb_compile_pascal,
and that works with either. That's my impression from quickly