unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: "Óscar Fuentes" <ofv@wanadoo.es>
To: Alan Mackenzie <acm@muc.de>
Cc: 7181@debbugs.gnu.org
Subject: bug#7181: 24.0.50; args-out-of-range while reverting C++ header file
Date: Sat, 09 Oct 2010 15:56:39 +0200	[thread overview]
Message-ID: <87ocb331wo.fsf@telefonica.net> (raw)
In-Reply-To: <87sk0f32pp.fsf@telefonica.net> ("Óscar Fuentes"'s message of "Sat, 09 Oct 2010 15:39:14 +0200")

[-- Attachment #1: Type: text/plain, Size: 457 bytes --]

With the attached files the problem can be reproduced predictability:

Save the attached files b.h.master and b.h.next to a directory and cd to
it.

$ emacs -Q &
$ cp b.h.master b.h
C-x C-f b.h
$ cp b.h.next b.h
M-x revert-buffer

and the args-out-of-range error pops:

c-clear-char-property-with-value-function: Args out of range: 166, 453

I was unable to try with the latest Emacs sources because the build is
broken. My Emacs is from the 16 September.


[-- Attachment #2: b.h.master --]
[-- Type: application/octet-stream, Size: 452 bytes --]

#ifndef BASICOPS_H_F902161C
#define BASICOPS_H_F902161C

#include "ffi.h"
#include <time.h>

LP0_NEW_TYPE_DEC_EXPORTED(unsigned char);
LP0_NEW_TYPE_DEC_EXPORTED(tm);

namespace lp0 {

struct Int : public OpBase0<int> {};

struct CastCharToStringOP : public OpBase1<std::string, char> {
  static void w(std::string *r, char v) {
    std::string t;
    t += v;
    FFIRetClass(r, t);
  }
};

} // namespace lp0

#endif /* #ifndef BASICOPS_H_F902161C */ 

[-- Attachment #3: b.h.next --]
[-- Type: application/octet-stream, Size: 349 bytes --]

#ifndef BASICOPS_H_F902161C
#define BASICOPS_H_F902161C

#include "ffi.h"
#include <time.h>

namespace lp0 {

template <typename Derived, typename Base>
struct DynamicCastOp : public OpBase1<Derived*, Base*>
{
  static Derived* w(Base *p) {
    return dynamic_cast<Derived*>(p);
  }
};

} // namespace lp0

#endif /* #ifndef BASICOPS_H_F902161C */ 

  reply	other threads:[~2010-10-09 13:56 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-09  4:30 bug#7181: 24.0.50; args-out-of-range while reverting C++ header file Oscar Fuentes
2010-10-09  8:57 ` Eli Zaretskii
2010-10-09 13:39   ` Óscar Fuentes
2010-10-09 13:56     ` Óscar Fuentes [this message]
2010-10-09 21:13       ` Alan Mackenzie
     [not found]       ` <20101009211332.GA5486@muc.de>
2010-10-09 22:08         ` bug#7181: after-change-functions hook arguments (was: bug#7181: 24.0.50; args-out-of-range while reverting C++ header file) Óscar Fuentes
2010-10-09 23:33         ` bug#7181: 24.0.50; args-out-of-range while reverting C++ header file Stefan Monnier
2010-10-10 14:09       ` bug#7181: 24.0.50; args-out-of-range while reverting C++ header file. PATCH Alan Mackenzie
     [not found]       ` <20101010140958.GA5249@muc.de>
2010-10-10 18:40         ` Óscar Fuentes

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87ocb331wo.fsf@telefonica.net \
    --to=ofv@wanadoo.es \
    --cc=7181@debbugs.gnu.org \
    --cc=acm@muc.de \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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).