Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Randolph Chung <randolph@tausq.org>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [patch/rfa] Don't assume SIG32 in staticthreads.exp
Date: Mon, 28 Mar 2005 00:00:00 -0000	[thread overview]
Message-ID: <20050328000107.GA2007@nevyn.them.org> (raw)
In-Reply-To: <20041201065740.GA6359@tausq.org>

On Tue, Nov 30, 2004 at 10:57:40PM -0800, Randolph Chung wrote:
> ping?

This patch is fine.  Sorry about the delay.

> 
> In reference to a message from Randolph Chung, dated Nov 23:
> > SIGRTMIN is 37 on hppa-linux and hpux, instead of 32, which was assumed
> > by this test.
> > 
> > also depending on the version of libc, etc, "sem_post" may have a
> > different internal symbolic name. for example on my test setup it shows
> > up as "__new_sem_post". This seems to be reasonable, so i've relaxed the
> > name checking slightly.
> > 
> > Tested on hppa-linux. ok to apply?
> > 
> > randolph
> > 
> > 
> > 2004-11-23  Randolph Chung  <tausq@debian.org>
> > 
> > 	testsuite/
> > 
> > 	* gdb.threads/staticthreads.exp: Override signal to check for hppa.
> > 	Slightly relex "sem_post" name checking.
> > 
> > 
> > Index: testsuite/gdb.threads/staticthreads.exp
> > ===================================================================
> > RCS file: /cvs/src/src/gdb/testsuite/gdb.threads/staticthreads.exp,v
> > retrieving revision 1.1
> > diff -u -p -r1.1 staticthreads.exp
> > --- testsuite/gdb.threads/staticthreads.exp	1 Sep 2004 18:02:45 -0000	1.1
> > +++ testsuite/gdb.threads/staticthreads.exp	23 Nov 2004 22:42:11 -0000
> > @@ -62,10 +62,17 @@ gdb_test_multiple "continue" "$test" {
> >  # See if handle SIG32 helps (a little) with a static multi-threaded
> >  # program.
> >  
> > +set sig "SIG32"
> > +
> > +# SIGRTMIN is 37 on hppa-linux and hpux
> > +if [istarget hppa*-*-*] {
> > +  set sig "SIG37"
> > +}
> > +
> >  rerun_to_main
> > -gdb_test "handle SIG32 nostop noprint pass"
> > -set test "Handle SIG32 helps"
> > -gdb_test "continue" " sem_post .*" "handle SIG32 helps"
> > +gdb_test "handle $sig nostop noprint pass"
> > +set test "Handle $sig helps"
> > +gdb_test "continue" " .*sem_post .*" "handle $sig helps"
> >  
> >  
> >  # See if info threads produces anything approaching a thread list.
> > -- 
> > Randolph Chung
> > Debian GNU/Linux Developer, hppa/ia64 ports
> > http://www.tausq.org/
> -- 
> Randolph Chung
> Debian GNU/Linux Developer, hppa/ia64 ports
> http://www.tausq.org/
> 

-- 
Daniel Jacobowitz
CodeSourcery, LLC


  reply	other threads:[~2005-03-28  0:00 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-23 22:46 Randolph Chung
2004-12-01  6:57 ` Randolph Chung
2005-03-28  0:00   ` Daniel Jacobowitz [this message]
2005-04-30 19:51     ` 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=20050328000107.GA2007@nevyn.them.org \
    --to=drow@false.org \
    --cc=gdb-patches@sources.redhat.com \
    --cc=randolph@tausq.org \
    /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