public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dafrabbit at yahoo dot com" <sourceware-bugzilla@sources.redhat.com>
To: glibc-bugs@sources.redhat.com
Subject: [Bug libc/366] Compiling on 64-bit yields segmentation fault when run, on 32-bit runs fine.
Date: Fri, 03 Sep 2004 13:01:00 -0000	[thread overview]
Message-ID: <20040903130141.24080.qmail@sourceware.org> (raw)
In-Reply-To: <20040903023911.366.dafrabbit@yahoo.com>


------- Additional Comments From dafrabbit at yahoo dot com  2004-09-03 13:01 -------
(In reply to comment #3)
> Well, if you really need two vprintf calls, you can use
>        va_list ap2;
>        va_copy (ap2, ap);
>        vfprintf(out_fp, fmt, ap);
>        vfprintf(log_stream_g, fmt, ap2);
>        va_end (ap2);
> 

Well, you then make it difficult to do the task to pass variable number of
arguments from one subroutine to another subroutine. I do't know whether C
forbids that. Your suggestion is to ask people not to use subroutines. I hope it
is not that restrictive.

-- 


http://sources.redhat.com/bugzilla/show_bug.cgi?id=366

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.


      parent reply	other threads:[~2004-09-03 13:01 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-03  2:39 [Bug libc/366] New: " dafrabbit at yahoo dot com
2004-09-03  2:39 ` [Bug libc/366] " dafrabbit at yahoo dot com
2004-09-03  4:23 ` aj at suse dot de
2004-09-03  7:41 ` jakub at redhat dot com
2004-09-03 13:01 ` dafrabbit at yahoo dot com [this message]

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=20040903130141.24080.qmail@sourceware.org \
    --to=sourceware-bugzilla@sources.redhat.com \
    --cc=glibc-bugs@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).