[#4745] Win32: Ruby & APR; build problems for Ruby Subversion SWIG bindings — Erik Huelsmann <ehuels@...>

Having taken upon me the task to provide a Windows build for

24 messages 2005/04/20
[#4746] Re: Win32: Ruby & APR; build problems for Ruby Subversion SWIG bindings — Austin Ziegler <halostatue@...> 2005/04/20

On 4/20/05, Erik Huelsmann <ehuels@gmail.com> wrote:

[#4747] Re: Win32: Ruby & APR; build problems for Ruby Subversion SWIG bindings — Erik Huelsmann <ehuels@...> 2005/04/20

Hi Austin,

[#4762] Re: Win32: Ruby & APR; build problems for Ruby Subversion SWIG bindings — nobu.nokada@... 2005/04/24

Hi,

[#4783] Re: Win32: Ruby & APR; build problems for Ruby Subversion SWIG bindings — Erik Huelsmann <ehuels@...> 2005/04/25

On 4/24/05, nobu.nokada@softhome.net <nobu.nokada@softhome.net> wrote:

[#4787] Re: Win32: Ruby & APR; build problems for Ruby Subversion SWIG bindings — nobu.nokada@... 2005/04/25

Hi,

[#4794] Re: Win32: Ruby & APR; build problems for Ruby Subversion SWIG bindings — Erik Huelsmann <ehuels@...> 2005/04/25

> > > Ruby is just using AC_TYPE_UID_T. So, using typedef for them,

[#4751] Illegal regexp causes segfault — Andrew Walrond <andrew@...>

irb(main):058:0> a = /\[([^]]*)\]/

13 messages 2005/04/22

Re: Illegal regexp causes segfault

From: ts <decoux@...>
Date: 2005-04-24 10:52:54 UTC
List: ruby-core #4767
>>>>> "t" == ts  <decoux@moulon.inra.fr> writes:

t>  Another example

 An example to see why I dont think that the problem is regex.c

uln% diff -u regex.c~ regex.c
--- regex.c~    2004-11-22 16:29:50.000000000 +0100
+++ regex.c     2005-04-24 12:37:32.000000000 +0200
@@ -1290,6 +1290,9 @@
 
   int options = bufp->options;
 
+  rb_warn("1");
+  rb_warn("2");
+
   bufp->fastmap_accurate = 0;
   bufp->must = 0;
   bufp->must_skip = 0;
uln% 

uln% gdb --quiet ./miniruby
Using host libthread_db library "/lib64/libthread_db.so.1".
(gdb) r -e '/[]]/'
Starting program: /opt/ts/ruby/ruby-1.8.2/miniruby -e '/[]]/'
-e:1: warning: 1

Program received signal SIGSEGV, Segmentation fault.
0x0000000000486f1d in warn_print (fmt=0x4a4d84 "2", args=0xffffffff)
    at error.c:126
126         rb_write_error2(buf, len);
(gdb) q
The program is running.  Exit anyway? (y or n) y
uln%


Guy Decoux

In This Thread