From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mail2-relais-roc.national.inria.fr (mail2-relais-roc.national.inria.fr [192.134.164.83])
	by walapai.inria.fr (8.13.6/8.13.6) with ESMTP id oBOEP7B7022121
	for <caml-list@sympa-roc.inria.fr>; Fri, 24 Dec 2010 15:25:07 +0100
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AuYBAM87FE3AbSoIe2dsb2JhbACDZJIwjhkWARYiBCCvNZBgDYETgzZ0BIUhiwk
X-IronPort-AV: E=Sophos;i="4.60,223,1291590000"; 
   d="scan'208";a="84675711"
Received: from einhorn.in-berlin.de ([192.109.42.8])
  by mail2-smtp-roc.national.inria.fr with ESMTP/TLS/DHE-RSA-AES256-SHA; 24 Dec 2010 15:25:02 +0100
X-Envelope-From: oliver@first.in-berlin.de
X-Envelope-To: <caml-list@yquem.inria.fr>
Received: from first (e178015038.adsl.alicedsl.de [85.178.15.38])
	(authenticated bits=0)
	by einhorn.in-berlin.de (8.13.6/8.13.6/Debian-1) with ESMTP id oBOEP1DF000567
	for <caml-list@yquem.inria.fr>; Fri, 24 Dec 2010 15:25:01 +0100
Received: by first (Postfix, from userid 1000)
	id 80435442214; Fri, 24 Dec 2010 15:25:01 +0100 (CET)
Date: Fri, 24 Dec 2010 15:25:01 +0100
From: oliver@first.in-berlin.de
To: caml-list@yquem.inria.fr
Message-ID: <20101224142501.GA3936@siouxsie>
References: <20101224040306.GA18312@siouxsie>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
In-Reply-To: <20101224040306.GA18312@siouxsie>
User-Agent: Mutt/1.5.20 (2009-06-14)
X-Scanned-By: MIMEDefang_at_IN-Berlin_e.V. on 192.109.42.8
Subject: Re: [Caml-list] PCRE: Invalid_argument("Pcre.get_offset_start:
 illegal offset")

On Fri, Dec 24, 2010 at 05:03:06AM +0100, oliver@first.in-berlin.de wrote:
> Hello,
> 
> I could not find a description in the PCRE-documentation,
> where this error comes from.
> 
> This does occur on my call to get_substring,
> but get_substring has documented exceptions,
> in case something goes wrong:
> 
>     * Invalid_argument if n is not in the range of the number of substrings.
>     * Not_found if the corresponding subpattern did not capture a substring.
[...]

It seems that trying to extract more substrings than are available,
this exception is raised.

This behaviour seems not to be documented.

Ciao,
   Oliver