[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[pdf-devel] *****POSSIBLE SPAM***** [PATCH] Error management in type4 fu
From: |
David Vazquez |
Subject: |
[pdf-devel] *****POSSIBLE SPAM***** [PATCH] Error management in type4 functions |
Date: |
Tue, 24 Feb 2009 19:51:58 +0100 |
SPAM Ranking: (5.9 points, 4.0 required)
Text in Spanish, Italian and English
SPANISH:
Spamassassin ha detectado este correo como posible spam. Aunque el sistema
descarta por comodidad los correos con valor mayor de 5, mantenemos un margen
de seguridad para evitar falsos positivos.
Si este correo es válido, para evitar que siga siendo detectado como spam,
reenvie este correo (manteniendo el adjunto original) a address@hidden
Si este correo es realmente SPAM, puede mejorar la eficiencia del sistema
enviando este correo (manteniendo el adjunto original) a address@hidden
ITALIAN:
Spamassassin ha catalogo questo email come Spam possibile. Anche se le poste
di scarto del sistema con lo Spam stimano la tomaia a 5, questo spacco di
sicurezza impedisce i positives falsi di goccia del sistema.
Se questa posta è utile, per impedire i positives falsi futuri con questo
genere di poste, prego di andata esso (con il collegamento originale) a
address@hidden
Se questa posta è Spam, potete contribuire ad aumentare l'esattezza della
spedizione del sistema questa posta (con il collegamento originale) a
ENGLISH:
Spamassassin has catalog this email as possible spam. Although the system
discard mails with spam value upper to 5, this security gap prevents system
drop false positives.
If this mail is useful, for prevent future false positives with this kind of
mails, please forward it (with the original attachment) to address@hidden
If this mail is realy SPAM, you can help to increase the accuracy of the
system forwarding this mail (with the original attachment) to address@hidden
------------------------------------------------------------------------------
Content preview: Hello, I send a patch for error management in type4 functions
task. The summary of the changes in the patch is: - Fix a bug in the real
numbers reader. I wrote parse_real function which works, though it does not
check overflows. It should be moved to the tokenizer module. [...]
Content analysis details: (5.9 points, 4.0 required)
pts rule name description
---- ---------------------- --------------------------------------------------
4.1 FH_HOST_EQ_DYNAMICIP Host is dynamicip
1.7 FUZZY_XPILL BODY: Attempt to obfuscate words in spam
0.0 BAYES_50 BODY: Bayesian spam probability is 40 to 60%
[score: 0.5000]
0.1 RDNS_DYNAMIC Delivered to trusted network by host with
dynamic-looking rDNS
The original message was not completely plain text, and may be unsafe to
open with some email clients; in particular, it may contain a virus,
or confirm that your address can receive spam. If you wish to view
it, it may be safer to save it to a file and open it with an editor.
--- Begin Message ---
Subject: |
[PATCH] Error management in type4 functions |
Date: |
Tue, 24 Feb 2009 19:51:58 +0100 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/23.0.60 (gnu/linux) |
Hello,
I send a patch for error management in type4 functions task.
The summary of the changes in the patch is:
- Fix a bug in the real numbers reader. I wrote parse_real function which
works, though it does not check overflows. It should be moved to the
tokenizer module.
- A code as the following compiled without errors, but the evaluator crashed:
{
...
{
...
}
...
} if
...
} if
}
The patch fixes this bug.
- pdf_fp_func_4_new reports errors correctly. It reports the position
of the error in the code too. I use the return value to do this.
- pdf_fp_func_eval reports interpretation errors in type 4 functions
correctly. I added some debug information to the function structure
in addition to the opcode. So, the evaluator can get the offset of a
interpretation error in the code, and inspect the current context
(the stack). However, the documentation does not describe the debug
structure yet.
- Add negative unit testing for the above-named.
Finally the type 4 evaluator does not check some `bad type' errors. The
reason is that two special real numbers stand for logic values:
#define REP_TRUE (1.202056903159594285399738162)
#define REP_FALSE (-15116315767.09215686274509804)
It is not very smart for me reporting errors so.
I wait you give me some feedback.
Thanks a lot,
David.
fp.patch
Description: patch
--- End Message ---
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- [pdf-devel] *****POSSIBLE SPAM***** [PATCH] Error management in type4 functions,
David Vazquez <=