The actual code in the PHP source is (main.c, 224):
aplog_error(NULL, 0, APLOG_ERR | APLOG_NOERRNO, php3_rqst->server,
log_message);
passing "%n" as log_message.
In PHP code:
<?
error_log("%n");
?>
I wasn't certain that this was related to the other bug report - just
thought it sounded similar.
-brian-
> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
> Sent: Friday, November 06, 1998 1:14 PM
> To: [EMAIL PROTECTED]; [EMAIL PROTECTED];
> [EMAIL PROTECTED]
> Subject: Re: apache-api/3355: ap_vformatter barfs on %n in log message
>
>
> [In order for any reply to be added to the PR database, ]
> [you need to include <[EMAIL PROTECTED]> in the Cc line ]
> [and leave the subject line UNCHANGED. This is not done]
> [automatically because of the potential for mail loops. ]
> [If you do not include this Cc, your reply may be ig- ]
> [nored unless you are responding to an explicit request ]
> [from a developer. ]
> [Reply only with text; DO NOT SEND ATTACHMENTS! ]
>
>
> Synopsis: ap_vformatter barfs on %n in log message
>
> State-Changed-From-To: open-feedback
> State-Changed-By: marc
> State-Changed-When: Fri Nov 6 10:14:22 PST 1998
> State-Changed-Why:
> Please give an exact example of a function call to log_error
> that uses %n and shows this problem.
>
> I'm not sure how this would be related to PR#2941 that you
> mention.
>
