Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Joel Brobecker <brobecker@gnat.com>
To: gdb-patches@sources.redhat.com
Subject: Re: [RFA/testsuite/ada] Refine expected output of start command
Date: Thu, 21 Oct 2004 03:56:00 -0000	[thread overview]
Message-ID: <20041021035605.GQ21300@gnat.com> (raw)
In-Reply-To: <20041021031426.GA21735@nevyn.them.org>

> Actually, it's been failing for me for a maybe related reason:
> 
> (gdb) start
> Breakpoint 1 at 0x8048ad0: file b~null_record.adb, line 99.
> Starting program: /opt/src/binutils/x86-as/gdb/testsuite/gdb.ada/null_record 
> main (argc=1, argv=(system.address) 0xbffff524, envp=(system.address) 0xbffff52c) at b~null_record.adb:99
> 99            Ensure_Reference : System.Address :=
> Ada_Main_Program_Name'Address;
> (gdb) PASS: gdb.ada/null_record.exp: start
> ptype empty
> type = function return int
> (gdb) FAIL: gdb.ada/null_record.exp: ptype on null record

Hmmm, no I don't think it's the same reason. And the test passes for
me.

Could you do an experiment for me, and tell me what the language
is after you load the executable? It should be auto,ada.  Same after
you've done the start.

Of maybe you could send me separately your executable, so I can take
a look...

> > 2004-10-20  Joel Brobecker  <brobecker@gnat.com>
> > 
> >         * gdb.ada/null_record.exp: Check where we stopped after
> >         sending the start command, instead of where the associated
> >         temporary breakpoint was inserted.
> > 
> > This causes the "start" test above to FAIL for now. But the fix for
> > this should be available soon.
> > 
> > OK to commit? (I verified that this PASSes again once I apply my fix)
> 
> This is OK.

Thanks, committed.

-- 
Joel


  reply	other threads:[~2004-10-21  3:56 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-21  2:49 Joel Brobecker
2004-10-21  3:38 ` Daniel Jacobowitz
2004-10-21  3:56   ` Joel Brobecker [this message]
2004-10-21  4:08 Michael Chastain

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=20041021035605.GQ21300@gnat.com \
    --to=brobecker@gnat.com \
    --cc=gdb-patches@sources.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