This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
RE: [PING] [RFC-v2] Use untested for macscp.exp if no macro information generated
> -----Message d'origine-----
> De?: gdb-patches-owner@sourceware.org [mailto:gdb-patches-
> owner@sourceware.org] De la part de Tom Tromey
> Envoyé?: Thursday, February 19, 2009 2:00 AM
> À?: Pierre Muller
> Cc?: 'Daniel Jacobowitz'; gdb-patches@sourceware.org
> Objet?: Re: [PING] [RFC-v2] Use untested for macscp.exp if no macro
> information generated
>
> >>>>> "Pierre" == Pierre Muller <muller@ics.u-strasbg.fr> writes:
>
> Pierre> I didn't get any feedback on this one.
>
> Sorry about that.
>
> Pierre> Should I resend it as a RFA?
>
> No need :)
>
> >> FAIL: gdb.base/macscp.exp: info macro WHERE after `list main'
> >> (undefined)
>
> It seems to me that it should be possible to check some macro
> expansion without running a "test", and thus not having any FAILs show
> up in the log.
>
> Is this too hard?
The problem is that this does not work
unless you already started the program,
loading it into memory with file is not enough...
And I didn't want to change the order of the tests
inside macscp.exp (there are a few tests
prior to starting, which I didn't want to touch).
One solution would be to start the debuggee,
check 'macro expand FIFTY_SEVEN' at that point,
flag as UNTESTED if this fails,
or restart gdb if the macro expand succeeds.
I thought about that when I first tried to
handle this, but was afraid that restarting
gdb once more for every tests done on all machines
just to avoid failures on machines that do
not support macros was not acceptable.
If you tell me it is OK,
I can try to resubmit a patch
doing so.
Pierre Muller
Pascal language support maintainer for GDB