public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: "Brian Ceccarelli" <brian@talusmusic.com>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: RE: c++/6774: printf("%lld") prints bad values
Date: Thu, 23 May 2002 07:56:00 -0000	[thread overview]
Message-ID: <20020523145602.2223.qmail@sources.redhat.com> (raw)

The following reply was made to PR c++/6774; it has been noted by GNATS.

From: "Brian Ceccarelli" <brian@talusmusic.com>
To: <rth@gcc.gnu.org>,
	<brian@talusmusic.com>,
	<gcc-bugs@gcc.gnu.org>,
	<gcc-prs@gcc.gnu.org>,
	<nobody@gcc.gnu.org>,
	<gcc-gnats@gcc.gnu.org>
Cc:  
Subject: RE: c++/6774: printf("%lld") prints bad values
Date: Thu, 23 May 2002 10:58:12 -0400

 I think I now discovered the real problem.
 
      pthread_t     id;
 
      status = pthread_create(&id, ...)
 
   The first call to pthread_create returns a valid thread ID 'id' argument.
 Subsequent pthread_create calls return 0 for id.   'status' is 0 in each
 case indicating successful thread creation.  (My multithreaded program works
 fine with the exception of that thread id.)
 
    I use a C++ object for each thread.  I was setting my object's ID
 attribute to the 'id' argument returned by pthread_create.   This works for
 the first thread I create, but not for subsequent threads.
 
    When I was printing out the thread_id, (which I later cast to long long),
 I was using "%lld".   So I thought %lld was the problem.  Since that wasn't
 the problem, I think the problem is with pthread_create.
 
    pthread_self() always returns the correct ID.    I now use this function
 everytime I need the thread-id.
 
    Do you want me to file a separate bug report on this?     Or am I going
 nuts again?   :)    I am on Red Hat Linux on an Intel platform.   Same thing
 happens on Mandrake Linux on Intel.
 
 
 
 Brian
 brian@talusmusic.com
 
 
 
 
 -----Original Message-----
 From: rth@gcc.gnu.org [mailto:rth@gcc.gnu.org]
 Sent: Thursday, May 23, 2002 2:42 AM
 To: brian@talusmusic.com; gcc-bugs@gcc.gnu.org; gcc-prs@gcc.gnu.org;
 nobody@gcc.gnu.org
 Subject: Re: c++/6774: printf("%lld") prints bad values
 
 
 Synopsis: printf("%lld") prints bad values
 
 State-Changed-From-To: open->closed
 State-Changed-By: rth
 State-Changed-When: Wed May 22 23:42:06 2002
 State-Changed-Why:
     Buggy test case.  You have a typo in your printf format.
     Should be "1 << %lld = %lld".  Using -Wall would have
     pointed this out:
 
     z.c: In function `main':
     z.c:11: warning: int format, different type arg (arg 2)
 
 
 
 http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&p
 r=6774
 


             reply	other threads:[~2002-05-23 14:56 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-23  7:56 Brian Ceccarelli [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-05-23  9:26 Richard Henderson
2002-05-23  5:46 Brian Ceccarelli
2002-05-22 23:42 rth
2002-05-22 17:46 brian

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=20020523145602.2223.qmail@sources.redhat.com \
    --to=brian@talusmusic.com \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=nobody@gcc.gnu.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).