Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@mvista.com>
To: Elena Zannoni <ezannoni@redhat.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFA/TESTSUITE] build schedlock.c on 64-bit platforms
Date: Thu, 10 Apr 2003 14:19:00 -0000	[thread overview]
Message-ID: <20030410141953.GA10379@nevyn.them.org> (raw)
In-Reply-To: <16021.31692.763468.4182@localhost.redhat.com>

On Thu, Apr 10, 2003 at 10:12:28AM -0400, Elena Zannoni wrote:
> Daniel Jacobowitz writes:
>  > On Tue, Apr 08, 2003 at 05:20:19PM -0400, Elena Zannoni wrote:
>  > > 
>  > > I was getting warnings when compiling the test on 64-bit because of the casts.
>  > > 
> 
>  > 
>  > Sigh, I was just sloppy writing this one.   Does it work if you pass
>  > &args[i] instead of messing with my_number?  That's a little more
>  > portable.
>  > 
> 
> Ok, how about this? But now get_current_thread in schedlock.exp
> doesn't work, because the output has changed. I am not sure I
> understand what it should be doing now. There is no way to get the
> thread number from the backtraces.

Oh, you're right - sorry for the wild goose chase.  I think your
previous patch with the cast to long is OK then.  The test isn't
terribly portable but it should be portable enough for our use.

> 
> elena
> 
> 
> 
> 
> Index: schedlock.c
> ===================================================================
> RCS file: /cvs/uberbaum/gdb/testsuite/gdb.threads/schedlock.c,v
> retrieving revision 1.2
> diff -u -p -r1.2 schedlock.c
> --- schedlock.c	23 Oct 2002 03:22:56 -0000	1.2
> +++ schedlock.c	10 Apr 2003 14:00:41 -0000
> @@ -18,19 +18,21 @@ int main() {
>      for (i = 0; i < NUM; i++)
>        {
>  	args[i] = 1;
> -	res = pthread_create(&threads[i], NULL, thread_function, (void *)i);
> +	res = pthread_create(&threads[i],
> +		             NULL,
> +			     thread_function,
> +			     (void *) &args[i]);
>        }
>  
>      /* schedlock.exp: last thread start.  */
>      args[i] = 1;
> -    thread_function ((void *) i);
> +    thread_function ((void *) &args[i]);
>  
>      exit(EXIT_SUCCESS);
>  }
>  
>  void *thread_function(void *arg) {
> -    int my_number = (int) arg;
> -    int *myp = &args[my_number];
> +    int *myp = (int *)arg;
>  
>      /* Don't run forever.  Run just short of it :)  */
>      while (*myp > 0)
> 
> 

-- 
Daniel Jacobowitz
MontaVista Software                         Debian GNU/Linux Developer


  reply	other threads:[~2003-04-10 14:19 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-08 21:16 Elena Zannoni
2003-04-09 13:13 ` Daniel Jacobowitz
2003-04-10 14:08   ` Elena Zannoni
2003-04-10 14:19     ` Daniel Jacobowitz [this message]
2003-04-10 14:35       ` Andrew Cagney
2003-04-10 15:16         ` Andreas Schwab
2003-04-10 15:20           ` Daniel Jacobowitz
2003-04-10 16:05             ` Elena Zannoni
2003-04-10 16:36               ` Andreas Schwab
2003-04-10 16:12             ` Andreas Schwab
2003-04-10 17:45               ` Andrew Cagney
2003-04-10 17:48                 ` Daniel Jacobowitz
2003-04-11  5:18       ` Michael Snyder
2003-04-15  1:48         ` Elena Zannoni
2003-04-15  2:06           ` Daniel Jacobowitz
2003-04-15  2:24             ` Elena Zannoni

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=20030410141953.GA10379@nevyn.them.org \
    --to=drow@mvista.com \
    --cc=ezannoni@redhat.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