Displaying 20 results from an estimated 70000 matches similar to: "message parser: Fixed infinite loop when parsing a specific message."
2013 May 24
1
[LLVMdev] Infinite loop parsing opt command line options
Hi all,
I am experiencing a problem managing the command line option of a set of
passes in my LLVM project.
Attached you find a toy project the triggers the problem.
The project is made up of two passes: "AnalysisPass" and "TransformPass".
"TransformPass" requires "AnalysisPass" and they both share a common
integer command line option called
2013 Nov 05
1
Message parser loops on certain messages (e.g. with a trailing CR character)
Hi,
dovecot's message parser enters an endless loop when fed with certain
multipart messages with stray CR characters.
parse_next_body_to_boundary() assumes the '\r' might be the beginning
of a boundary line, reducing the block size by one:
src/lib-mail/message-parser.c:
404 /* no linefeeds in this block. we can just skip it. */
405 ret = 0;
406
2008 Sep 16
1
another assertion failure in current 1.1 hg (1.1.3 was working fine) - file message-address.c: line 43 (parse_local_part): assertion failed: (ctx->parser.data != ctx->parser.end)
file message-address.c: line 43 (parse_local_part): assertion failed:
(ctx->parser.data != ctx->parser.end)
#0 0x001b3402 in __kernel_vsyscall ()
No symbol table info available.
#1 0x0043ed20 in raise () from /lib/libc.so.6
No symbol table info available.
#2 0x00440631 in abort () from /lib/libc.so.6
No symbol table info available.
#3 0x080f6968 in default_fatal_finish
2007 Mar 19
0
[898] branches/wxruby2/wxwidgets_282/swig/classes/App.i: Fix init of stock objects for Wx2.8 - was causing infinite loop +crash on OS X
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN"
"http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head><meta http-equiv="content-type" content="text/html; charset=utf-8" /><style type="text/css"><!--
#msg dl { border: 1px #006 solid; background: #369; padding:
2011 Mar 25
2
Regression in settings-parser.c (dovecot 2.0.11)
Hi,
one Fedora user sees regression in dovecot 2.0.11 (compared to prev. 2.0.9). There was change recently:
http://hg.dovecot.org/dovecot-2.0/diff/bc77e80947c0/src/lib-settings/settings-parser.c
which adds call to settings_find_key_nth(...., &parent_def,...). This function can set parent_def to NULL, but
there is no check for this situation in the code. So on next line if (parent_def->type
2008 Dec 13
2
mbox "Next message unexpectedly lost" bug fixed
Good news, everyone!
The most annoying bug in v1.1 series should finally be fixed by these
patches:
http://hg.dovecot.org/dovecot-1.1/rev/f28348c5201e
http://hg.dovecot.org/dovecot-1.1/rev/74c47fcfb420
http://hg.dovecot.org/dovecot-1.1/rev/a28520d26b5a
http://hg.dovecot.org/dovecot-1.1/rev/539f8d983285
http://hg.dovecot.org/dovecot-1.1/rev/9b7af230f9f0
They also make sure that mbox is never
2019 Jan 25
0
[klibc:update-dash] parser: Fix parsing of ${}
Commit-ID: 5e8e1a2d765473c0fe0321576e498fe114b76026
Gitweb: http://git.kernel.org/?p=libs/klibc/klibc.git;a=commit;h=5e8e1a2d765473c0fe0321576e498fe114b76026
Author: Herbert Xu <herbert at gondor.apana.org.au>
AuthorDate: Tue, 3 Apr 2018 00:40:25 +0800
Committer: Ben Hutchings <ben at decadent.org.uk>
CommitDate: Fri, 25 Jan 2019 02:57:21 +0000
[klibc] parser: Fix parsing of
2020 Mar 28
0
[klibc:update-dash] dash: parser: Fix parsing of ${}
Commit-ID: 8dfaea787acb1aaf1387af6a81904e0a57746985
Gitweb: http://git.kernel.org/?p=libs/klibc/klibc.git;a=commit;h=8dfaea787acb1aaf1387af6a81904e0a57746985
Author: Herbert Xu <herbert at gondor.apana.org.au>
AuthorDate: Tue, 3 Apr 2018 00:40:25 +0800
Committer: Ben Hutchings <ben at decadent.org.uk>
CommitDate: Sat, 28 Mar 2020 21:42:55 +0000
[klibc] dash: parser: Fix
2009 Nov 25
1
Question R's parser : - parsing "x=\n 1"
Hello
I was reading the source main/src/gram.y and had one question, how does R parse
x =
1
According the grammar:
prog : END_OF_INPUT { return 0; }
| '\n' { return xxvalue(NULL,2,NULL); }
| expr_or_assign '\n' { return xxvalue($1,3,&@1); }
| expr_or_assign ';' { return xxvalue($1,4,&@1); }
| error { YYABORT; }
;
So this should be of the 3rd
2014 Jul 22
0
ASN1 parser: Error in DER parsing
openssl "blesses" my cert chain, but samba has an issue with it.
TLS failed to initialise certfile /var/lib/samba/private/tls/standard.k12.ca.us.crt and keyfile /var/lib/samba/private/tls/standard.k12.ca.us.key - ASN1 parser: Error in DER parsing.
openssl verify -CAfile gd_bundle.crt standard.k12.ca.us.crt
standard.k12.ca.us.crt: OK
Anyone know where I went wrong? incorrect cert
2008 Oct 23
4
Possible header parsing problem
Hi,
I ran into a problem wherein my mail client (RoundCube) would not
display a message from a Dovecot IMAP server (claiming that the message
had no content). The raw source of the message looked fine, but the body
structure returned by Dovecot only had the first text/plain part and not
the alternative text/html part. The message looks like:
... headers removed ...
X-Mailer: Lotus
2011 Nov 09
1
[LLVMdev] Help to debug the miscompilation of a loop into an infinite loop
Hi,
I found out that dumping the IR to disk and taking it back makes
a miscompile disappear. I would appreciate your help on how
to narrow down such a bug.
Here are more details: when I compile one of the SPEC benchmarks
with clang at -O3, the code is miscompiled producing an infinite loop.
If I split the compilation using -emit-llvm and then finish the compilation
from the .ll file with llc (I
2012 Nov 14
2
[LLVMdev] Is infinite empty loop dead code?
On Wed, Nov 14, 2012 at 03:32:53PM +0800, 陳韋任 (Wei-Ren Chen) wrote:
> On Tue, Nov 13, 2012 at 11:23:02PM -0800, Shuxin Yang wrote:
> > Hi, All:
> >
> > Is it legal to delete empty infinite loop like this : "while(1) {}"?
> > It is interesting that both llvm and gcc keep the loop, however Open64
> > delete it.
>
> I think it's illegal
2012 Nov 14
0
[LLVMdev] Is infinite empty loop dead code?
On Tue, Nov 13, 2012 at 11:23:02PM -0800, Shuxin Yang wrote:
> Hi, All:
>
> Is it legal to delete empty infinite loop like this : "while(1) {}"?
> It is interesting that both llvm and gcc keep the loop, however Open64
> delete it.
I think it's illegal to delete such infinite loop, perhapes you should
file a bug report to open64. That's my 2 cents.
2012 Nov 14
0
[LLVMdev] Is infinite empty loop dead code?
Hi Shuxin,
> Is it legal to delete empty infinite loop like this : "while(1) {}"?
> It is interesting that both llvm and gcc keep the loop, however Open64 delete it.
this is an endless source of discussion. I suggest you read the GCC and LLVM
mailing list archives if you want to find out more about it.
Ciao, Duncan.
> If it is safe to delete this loop, it would be
2012 Nov 14
0
[LLVMdev] Is infinite empty loop dead code?
Following loop (in asm) is often seen in embedded programs. It is used
to delay for certain amount of time.
If it were not written in asm, compiler would blindly delete the entire
loop. How can compiler know such DCE
betray program intention?
for (i = 0; i < N; i++) { nop; nop; nop }
I guess in the gray area, if programmer do not want compiler do
something he doesn't expect,
he/she
2007 May 27
1
DO NOT REPLY [Bug 4664] New: Infinite loop on files > 2Gb
https://bugzilla.samba.org/show_bug.cgi?id=4664
Summary: Infinite loop on files > 2Gb
Product: rsync
Version: 2.6.9
Platform: Other
OS/Version: Windows XP
Status: NEW
Severity: normal
Priority: P3
Component: core
AssignedTo: wayned@samba.org
ReportedBy: steven.hartland@multiplay.co.uk
2006 Apr 28
2
cannot kill infinite loop. please help
an error in my rails code caused the framework to send an infinite
number of SQL calls to the database. I killed the webrick server,
restarted postgres, deleted the /tmp file in my rails application,
deleted the bad code, restarted firefox, restarted the webrick server.
All to no avail.
As soon as I try loading my application, the infinite recursion starts
again.
I can no longer work. This
2003 Oct 18
1
Res: Nmbd in a infinite loop, doing nothing and sucking 99%CPU (really)
Hi, Tim
Not even one ocurrence of "wins support" on my smb.conf
-----Mensagem original-----
De: Tim Kelley [mailto:tpk@r00tserverz.net]
Enviada em: s?bado, 18 de outubro de 2003 11:09
Para: Reinaldo Brand?o Gomes
Cc: samba@samba.org
Assunto: Re: [Samba] Nmbd in a infinite loop, doing nothing and sucking 99%CPU (really)
On Saturday 18 October 2003 9:03 am, Reinaldo Brand?o Gomes
2014 Apr 13
1
[Bug 10551] New: Daemon infinite loop when no matched user in secrets
https://bugzilla.samba.org/show_bug.cgi?id=10551
Summary: Daemon infinite loop when no matched user in secrets
Product: rsync
Version: 3.1.1
Platform: x64
OS/Version: Linux
Status: NEW
Severity: major
Priority: P5
Component: core
AssignedTo: wayned at samba.org
ReportedBy: ryan at