Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@mvista.com>
To: gdb@sources.redhat.com
Subject: Re: A testsuite update, for the curious
Date: Tue, 14 Jan 2003 17:26:00 -0000	[thread overview]
Message-ID: <20030114172718.GA20666@nevyn.them.org> (raw)
In-Reply-To: <200301140818.h0E8IbE30657@duracef.shout.net>

On Tue, Jan 14, 2003 at 02:18:37AM -0600, Michael Elizabeth Chastain wrote:
> Daniel Jacobowitz writes:
> > One FAIL from gdb.gdb/complaints.exp.
> 
> Hey, I'm not getting any FAILs from gdb.gdb/complaints.exp in any
> of my tested configurations.

It is dependent (like the rest of gdb.gdb/) on the compiler used to
build gdb and the optimization level.  Do you use 2.95.3 +
optimization to build any of your GDB's?

> > a testsuite bug that only shows up with a relative path to configure,
> 
> You probably already figured this out:
> 
>   # TODO: gdb.base/corefile.exp cannot handle relative objdir
>   #       it does "cd ${objdir}/${subdir}; ${binfile};" when
>   #       ${binfile} == ${objdir}/${subdir}/${testfile}.
> 
> The fix is probably just s/${binfile}/${testfile} .
> 
> BTW I am unable to run corefile.exp on native i686-pc-linux-gnu red-hat-8.0
> because red hat 8.0 turns on the kernel flag for core file names so that
> the names are 'core.12345' instead of 'core'.

Oh, very neat.  I don't know why I didn't ever see this one; I was
referring to one of the new MI tests.

I get a lot of garbage core.NUMBER files but they're from one of the
other tests... a threaded one I think.

> > And something else is wrong in print-threads.exp; I occasionally see a
> > SIGSEGV in the testsuite log.  But I can't reproduce it often enough to
> > get a good look at it.
> 
> I get sporadic ERRORs in gdb.trace/actions.exp.  I am not seeing this
> behavior in print-threads.exp and I am running 100+ of them per week
> (I run a lot of "infrastructure" test runs that I don't publish, but I
> would notice a bunch of core-dump-induced madness).  I do see one other
> print-threads.exp problem that manifests with sourceware TCL+Expect+Dejagnu
> and does not manifest with stock TCL+Expect+Dejagnu.  So it's quite
> possible that there are races that never get scheduled depending on
> subtle things like the version of Expect that you test with.

I've never seen the ERRORs; how bizarre... I'll look at your logs
sometime.

-- 
Daniel Jacobowitz
MontaVista Software                         Debian GNU/Linux Developer


  reply	other threads:[~2003-01-14 17:26 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-14  8:19 Michael Elizabeth Chastain
2003-01-14 17:26 ` Daniel Jacobowitz [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-01-14 17:36 Michael Elizabeth Chastain
2003-01-14  5:04 Daniel Jacobowitz
2003-01-14  6:50 ` Daniel Jacobowitz
2003-01-14  7:01   ` Daniel Jacobowitz

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=20030114172718.GA20666@nevyn.them.org \
    --to=drow@mvista.com \
    --cc=gdb@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