segfaults on mandrake...

Discussion in 'Ruby' started by Ferenc Engard, Jan 18, 2004.

  1. Hello,

    I have reproducible, but not constant segfaults (sometimes hangups) on
    Mandrake 9.2 (download edition, or what -- I do not use it
    frequently).

    The packages:

    ruby-tk-1.8.1-1mdk
    ruby-mysql-2.4.5-1
    ruby-dbi-0.0.21-1
    ruby-1.8.1-1mdk

    Ruby version:
    ruby 1.8.1 (2003-12-25) [i586-linux-gnu]

    Some segfault places:

    /usr/lib/ruby/site_ruby/1.8/DBD/Mysql/Mysql.rb:418: [BUG] Segmentation
    fault
    ruby 1.8.1 (2003-12-25) [i586-linux-gnu]

    /usr/lib/ruby/site_ruby/1.8/DBD/Mysql/Mysql.rb:425: [BUG] Segmentation
    fault
    ruby 1.8.1 (2003-12-25) [i586-linux-gnu]

    /usr/lib/ruby/site_ruby/1.8/dbi/row.rb:39: [BUG] Segmentation fault
    ruby 1.8.1 (2003-12-25) [i586-linux-gnu]

    (eval):762: [BUG] Segmentation fault
    ruby 1.8.1 (2003-12-25) [i586-linux-gnu]

    Sometimes also segfaults in my code. The program makes heavy
    DBI::StatementHandle using (and output to stdout) when the crash
    occurs.

    This is a P4 celeron 2100MHz machine. On my home machine, which is a
    P233, which is a also a 1.8.1 (2003-11-11), the crash never occurs.

    Any tips?

    Ferenc
    Ferenc Engard, Jan 18, 2004
    #1
    1. Advertising

  2. Ferenc Engard

    Guest

    Hi,

    At Mon, 19 Jan 2004 06:51:04 +0900,
    Ferenc Engard wrote:
    > This is a P4 celeron 2100MHz machine. On my home machine, which is a
    > P233, which is a also a 1.8.1 (2003-11-11), the crash never occurs.


    Sounds like concerning to pthread support. Try with CVS HEAD
    version. And can't you get stack trace from core?

    --
    Nobu Nakada
    , Jan 18, 2004
    #2
    1. Advertising

  3. On Mon, 19 Jan 2004 wrote:

    >Hi,
    >
    >At Mon, 19 Jan 2004 06:51:04 +0900,
    >Ferenc Engard wrote:
    >> This is a P4 celeron 2100MHz machine. On my home machine, which is a
    >> P233, which is a also a 1.8.1 (2003-11-11), the crash never occurs.

    >
    >Sounds like concerning to pthread support. Try with CVS HEAD
    >version. And can't you get stack trace from core?


    I have tried on another debian with the actual ruby package
    (2003-12-27), and it didn't segfaulted. So it is possible that the
    problem is not with ruby.

    How can I core dump? Right now, I am not at the machine, so apologize
    if it dumps core automatically.

    If it is possible, I wouldn't try the CVS version, as I have a real
    tight deadline to deliver my program (hence this new distro-related
    problem).

    I guess my glibc (pthreads) version is 2.3.2.

    It is a real big problem to me, if I cannot install my script to these
    mdk boxes... :(((

    Thanks,
    Ferenc
    Ferenc Engard, Jan 19, 2004
    #3
  4. Hello,

    I still cannot know how to dump core, but running 3 times from gdb
    caused 3 segfaults in different places.

    I am totally helpless. What can I do?

    Ferenc

    Here are the backtraces (sorry about the long mail):

    (no debugging symbols found)...(no debugging symbols found)...
    Program received signal SIGSEGV, Segmentation fault.
    0x401aef9f in realloc () from /lib/i686/libc.so.6
    (gdb) bt
    #0 0x401aef9f in realloc () from /lib/i686/libc.so.6
    #1 0x40061e68 in ruby_xrealloc () from /usr/lib/libruby.so.1.8
    #2 0x400ad33a in rb_str_update () from /usr/lib/libruby.so.1.8
    #3 0x400505a8 in rb_frame_last_func () from /usr/lib/libruby.so.1.8
    #4 0x40045cb5 in rb_eval_string () from /usr/lib/libruby.so.1.8
    #5 0x4004ded9 in rb_rescue2 () from /usr/lib/libruby.so.1.8
    #6 0x40018822 in lib_watchdog_ensure ()
    from /usr/lib/ruby/1.8/i586-linux-gnu/tcltklib.so
    #7 0x4004e11e in rb_ensure () from /usr/lib/libruby.so.1.8
    #8 0x40018905 in lib_watchdog_ensure ()
    from /usr/lib/ruby/1.8/i586-linux-gnu/tcltklib.so
    (gdb)



    (no debugging symbols found)...(no debugging symbols found)...
    Program received signal SIGSEGV, Segmentation fault.
    0x400a9fd0 in st_free_table () from /usr/lib/libruby.so.1.8
    (gdb) bt
    #0 0x400a9fd0 in st_free_table () from /usr/lib/libruby.so.1.8
    #1 0x4006342f in rb_gc_force_recycle () from /usr/lib/libruby.so.1.8
    #2 0x40063188 in rb_gc_mark () from /usr/lib/libruby.so.1.8
    #3 0x400638b9 in rb_gc () from /usr/lib/libruby.so.1.8
    #4 0x40062269 in rb_newobj () from /usr/lib/libruby.so.1.8
    #5 0x4004ecf3 in rb_with_disable_interrupt () from /usr/lib/libruby.so.1.8
    #6 0x4004f59f in rb_with_disable_interrupt () from /usr/lib/libruby.so.1.8
    #7 0x400486bc in rb_Array () from /usr/lib/libruby.so.1.8
    #8 0x4004adef in rb_Array () from /usr/lib/libruby.so.1.8
    #9 0x4004cf0a in rb_iterator_p () from /usr/lib/libruby.so.1.8
    #10 0x4004d217 in rb_yield_values () from /usr/lib/libruby.so.1.8
    #11 0x400408e9 in rb_each () from /usr/lib/libruby.so.1.8
    #12 0x4004ce97 in rb_iterator_p () from /usr/lib/libruby.so.1.8
    #13 0x4004d151 in rb_yield () from /usr/lib/libruby.so.1.8
    #14 0x40033472 in rb_ary_each () from /usr/lib/libruby.so.1.8
    #15 0x4005c1fa in rb_throw () from /usr/lib/libruby.so.1.8
    #16 0x4004f1fd in rb_with_disable_interrupt () from /usr/lib/libruby.so.1.8
    #17 0x4004f59f in rb_with_disable_interrupt () from /usr/lib/libruby.so.1.8
    #18 0x4004f903 in rb_funcall () from /usr/lib/libruby.so.1.8
    #19 0x4003f957 in rb_each () from /usr/lib/libruby.so.1.8
    #20 0x4004da29 in rb_iterate () from /usr/lib/libruby.so.1.8
    #21 0x40040963 in rb_each () from /usr/lib/libruby.so.1.8
    #22 0x4005c1fa in rb_throw () from /usr/lib/libruby.so.1.8
    #23 0x4004f1fd in rb_with_disable_interrupt () from /usr/lib/libruby.so.1.8
    #24 0x4004f59f in rb_with_disable_interrupt () from /usr/lib/libruby.so.1.8
    #25 0x400486bc in rb_Array () from /usr/lib/libruby.so.1.8
    #26 0x4004b523 in rb_Array () from /usr/lib/libruby.so.1.8
    #27 0x4004ef97 in rb_with_disable_interrupt () from /usr/lib/libruby.so.1.8
    #28 0x4004f59f in rb_with_disable_interrupt () from /usr/lib/libruby.so.1.8
    #29 0x400486bc in rb_Array () from /usr/lib/libruby.so.1.8
    #30 0x4004b4e5 in rb_Array () from /usr/lib/libruby.so.1.8
    #31 0x4004ef97 in rb_with_disable_interrupt () from /usr/lib/libruby.so.1.8
    #32 0x4004f59f in rb_with_disable_interrupt () from /usr/lib/libruby.so.1.8
    #33 0x400486bc in rb_Array () from /usr/lib/libruby.so.1.8
    #34 0x4004993f in rb_Array () from /usr/lib/libruby.so.1.8
    #35 0x4004ef97 in rb_with_disable_interrupt () from /usr/lib/libruby.so.1.8
    #36 0x4004f59f in rb_with_disable_interrupt () from /usr/lib/libruby.so.1.8
    #37 0x400486bc in rb_Array () from /usr/lib/libruby.so.1.8
    #38 0x4004870d in rb_Array () from /usr/lib/libruby.so.1.8
    ---Type <return> to continue, or q <return> to quit---
    #39 0x4004870d in rb_Array () from /usr/lib/libruby.so.1.8
    #40 0x4004870d in rb_Array () from /usr/lib/libruby.so.1.8
    #41 0x4004993f in rb_Array () from /usr/lib/libruby.so.1.8
    #42 0x4004cf0a in rb_iterator_p () from /usr/lib/libruby.so.1.8
    #43 0x4004d151 in rb_yield () from /usr/lib/libruby.so.1.8
    #44 0x40079204 in rb_fix2str () from /usr/lib/libruby.so.1.8
    #45 0x4005c1fa in rb_throw () from /usr/lib/libruby.so.1.8
    #46 0x4004f1fd in rb_with_disable_interrupt () from /usr/lib/libruby.so.1.8
    #47 0x4004f59f in rb_with_disable_interrupt () from /usr/lib/libruby.so.1.8
    #48 0x400486bc in rb_Array () from /usr/lib/libruby.so.1.8
    #49 0x4004b523 in rb_Array () from /usr/lib/libruby.so.1.8
    #50 0x4004ef97 in rb_with_disable_interrupt () from /usr/lib/libruby.so.1.8
    #51 0x4004f59f in rb_with_disable_interrupt () from /usr/lib/libruby.so.1.8
    #52 0x400486bc in rb_Array () from /usr/lib/libruby.so.1.8
    #53 0x40048965 in rb_Array () from /usr/lib/libruby.so.1.8
    #54 0x4004ef97 in rb_with_disable_interrupt () from /usr/lib/libruby.so.1.8
    #55 0x4004f59f in rb_with_disable_interrupt () from /usr/lib/libruby.so.1.8
    #56 0x400486bc in rb_Array () from /usr/lib/libruby.so.1.8
    #57 0x4004cf0a in rb_iterator_p () from /usr/lib/libruby.so.1.8
    #58 0x400548a1 in rb_f_lambda () from /usr/lib/libruby.so.1.8
    #59 0x400549c8 in rb_f_lambda () from /usr/lib/libruby.so.1.8
    #60 0x4005c1c6 in rb_throw () from /usr/lib/libruby.so.1.8
    #61 0x4004f1fd in rb_with_disable_interrupt () from /usr/lib/libruby.so.1.8
    #62 0x4004f59f in rb_with_disable_interrupt () from /usr/lib/libruby.so.1.8
    #63 0x4004f9ab in rb_funcall2 () from /usr/lib/libruby.so.1.8
    #64 0x400462d0 in rb_eval_cmd () from /usr/lib/libruby.so.1.8
    #65 0x4001f966 in _init () from /usr/lib/ruby/1.8/i586-linux-gnu/tkutil.so
    #66 0x4005c1e4 in rb_throw () from /usr/lib/libruby.so.1.8
    #67 0x4004f1fd in rb_with_disable_interrupt () from /usr/lib/libruby.so.1.8
    #68 0x4004f59f in rb_with_disable_interrupt () from /usr/lib/libruby.so.1.8
    #69 0x400486bc in rb_Array () from /usr/lib/libruby.so.1.8
    #70 0x4004cf0a in rb_iterator_p () from /usr/lib/libruby.so.1.8
    #71 0x400548a1 in rb_f_lambda () from /usr/lib/libruby.so.1.8
    #72 0x400549c8 in rb_f_lambda () from /usr/lib/libruby.so.1.8
    #73 0x4005c1c6 in rb_throw () from /usr/lib/libruby.so.1.8
    #74 0x4004f1fd in rb_with_disable_interrupt () from /usr/lib/libruby.so.1.8
    #75 0x4004f59f in rb_with_disable_interrupt () from /usr/lib/libruby.so.1.8
    #76 0x4004f9ab in rb_funcall2 () from /usr/lib/libruby.so.1.8
    #77 0x400462d0 in rb_eval_cmd () from /usr/lib/libruby.so.1.8
    ---Type <return> to continue, or q <return> to quit---
    #78 0x4001f966 in _init () from /usr/lib/ruby/1.8/i586-linux-gnu/tkutil.so
    #79 0x4005c1e4 in rb_throw () from /usr/lib/libruby.so.1.8
    #80 0x4004f1fd in rb_with_disable_interrupt () from /usr/lib/libruby.so.1.8
    #81 0x4004f59f in rb_with_disable_interrupt () from /usr/lib/libruby.so.1.8
    #82 0x400486bc in rb_Array () from /usr/lib/libruby.so.1.8
    #83 0x4004ae1b in rb_Array () from /usr/lib/libruby.so.1.8
    #84 0x4004ef97 in rb_with_disable_interrupt () from /usr/lib/libruby.so.1.8
    #85 0x4004f59f in rb_with_disable_interrupt () from /usr/lib/libruby.so.1.8
    #86 0x400486bc in rb_Array () from /usr/lib/libruby.so.1.8
    #87 0x4004ef97 in rb_with_disable_interrupt () from /usr/lib/libruby.so.1.8
    #88 0x4004f59f in rb_with_disable_interrupt () from /usr/lib/libruby.so.1.8
    #89 0x400486bc in rb_Array () from /usr/lib/libruby.so.1.8
    #90 0x4004ef97 in rb_with_disable_interrupt () from /usr/lib/libruby.so.1.8
    #91 0x4004f59f in rb_with_disable_interrupt () from /usr/lib/libruby.so.1.8
    #92 0x400486bc in rb_Array () from /usr/lib/libruby.so.1.8
    #93 0x400503e1 in rb_frame_last_func () from /usr/lib/libruby.so.1.8
    #94 0x40045cb5 in rb_eval_string () from /usr/lib/libruby.so.1.8
    #95 0x4004ded9 in rb_rescue2 () from /usr/lib/libruby.so.1.8
    #96 0x40018822 in lib_watchdog_ensure ()
    from /usr/lib/ruby/1.8/i586-linux-gnu/tcltklib.so
    #97 0x4004e11e in rb_ensure () from /usr/lib/libruby.so.1.8
    #98 0x40018905 in lib_watchdog_ensure ()
    from /usr/lib/ruby/1.8/i586-linux-gnu/tcltklib.so



    (no debugging symbols found)...(no debugging symbols found)...
    Program received signal SIGSEGV, Segmentation fault.
    0x401afb5d in mallopt () from /lib/i686/libc.so.6
    (gdb) bt
    #0 0x401afb5d in mallopt () from /lib/i686/libc.so.6
    #1 0x401aecb8 in malloc () from /lib/i686/libc.so.6
    (gdb)
    Ferenc Engard, Jan 19, 2004
    #4
  5. Ferenc Engard

    Guest

    Hi,

    At Tue, 20 Jan 2004 07:42:41 +0900,
    Ferenc Engard wrote:
    > I still cannot know how to dump core, but running 3 times from gdb
    > caused 3 segfaults in different places.


    Try "ulimit -c unlimited" to make core.

    > Here are the backtraces (sorry about the long mail):


    All seem related with GC. I guess it might be fixed in CVS
    HEAD, or disapper by configuring with --disable-pthread.

    --
    Nobu Nakada
    , Jan 19, 2004
    #5
  6. wrote:
    >
    > Hi,
    >
    > At Tue, 20 Jan 2004 07:42:41 +0900,
    > Ferenc Engard wrote:
    > > I still cannot know how to dump core, but running 3 times from gdb
    > > caused 3 segfaults in different places.

    >
    > Try "ulimit -c unlimited" to make core.
    >
    > > Here are the backtraces (sorry about the long mail):

    >
    > All seem related with GC. I guess it might be fixed in CVS
    > HEAD, or disapper by configuring with --disable-pthread.


    Does it affect multithreading (i.e., tk)?

    Anyway, it seems that the problem exists only on mandrake, even with
    newer ruby than on my debian box. The latest one was tried is
    2003-12-27, and on debian I was happy with 2003-11-11. Are you sure
    compiling the HEAD version solves the problem?

    Nobody uses mandrake here?

    Ferenc
    Ferenc Engard, Jan 20, 2004
    #6
  7. Hi,

    In message "Re: segfaults on mandrake..."
    on 04/01/20, Ferenc Engard <> writes:
    |>
    |> All seem related with GC. I guess it might be fixed in CVS
    |> HEAD, or disapper by configuring with --disable-pthread.
    |
    |Does it affect multithreading (i.e., tk)?

    Depends on your platform. If your tcltk is linked with -lpthread,
    -enable-pthread is necessary.

    matz.
    Yukihiro Matsumoto, Jan 20, 2004
    #7
  8. Ferenc Engard

    Guest

    Hi,

    At Tue, 20 Jan 2004 15:14:49 +0900,
    Ferenc Engard wrote:
    > > > Here are the backtraces (sorry about the long mail):

    > >
    > > All seem related with GC. I guess it might be fixed in CVS
    > > HEAD, or disapper by configuring with --disable-pthread.

    >
    > Does it affect multithreading (i.e., tk)?


    It should have worked before --enable-pthread was introduced.

    > Anyway, it seems that the problem exists only on mandrake, even with
    > newer ruby than on my debian box. The latest one was tried is
    > 2003-12-27, and on debian I was happy with 2003-11-11. Are you sure
    > compiling the HEAD version solves the problem?


    Though I'm not sure, there are some fixes which are not
    backported to 1.8 yet.

    --
    Nobu Nakada
    , Jan 20, 2004
    #8
  9. On Tue, 20 Jan 2004, Yukihiro Matsumoto wrote:

    >Hi,
    >
    >In message "Re: segfaults on mandrake..."
    > on 04/01/20, Ferenc Engard <> writes:
    >|>
    >|> All seem related with GC. I guess it might be fixed in CVS
    >|> HEAD, or disapper by configuring with --disable-pthread.
    >|
    >|Does it affect multithreading (i.e., tk)?
    >
    >Depends on your platform. If your tcltk is linked with -lpthread,
    >-enable-pthread is necessary.


    Yes, it does. :-(

    fery@cirmi:~$ ldd /usr/lib/libtk8.4.so.0
    libpthread.so.0 => /lib/libpthread.so.0 (0x400e0000)
    [...]


    Ferenc
    Ferenc Engard, Jan 20, 2004
    #9
  10. On Tue, 20 Jan 2004 wrote:

    >Hi,
    >
    >At Tue, 20 Jan 2004 15:14:49 +0900,
    >Ferenc Engard wrote:
    >> > > Here are the backtraces (sorry about the long mail):
    >> >
    >> > All seem related with GC. I guess it might be fixed in CVS
    >> > HEAD, or disapper by configuring with --disable-pthread.

    >>
    >> Does it affect multithreading (i.e., tk)?

    >
    >It should have worked before --enable-pthread was introduced.
    >
    >> Anyway, it seems that the problem exists only on mandrake, even with
    >> newer ruby than on my debian box. The latest one was tried is
    >> 2003-12-27, and on debian I was happy with 2003-11-11. Are you sure
    >> compiling the HEAD version solves the problem?

    >
    >Though I'm not sure, there are some fixes which are not
    >backported to 1.8 yet.


    As there were no other suggestions, I try to do my first ruby
    compiling... :((

    Mandrake uses many dist-specific patches to libc. Cannot be the
    problem connected with one of these patches?

    Ferenc
    Ferenc Engard, Jan 20, 2004
    #10
  11. Ferenc Engard

    Mike Stok Guest

    In article <>,
    Ferenc Engard <> wrote:
    >Does it affect multithreading (i.e., tk)?
    >
    >Anyway, it seems that the problem exists only on mandrake, even with
    >newer ruby than on my debian box. The latest one was tried is
    >2003-12-27, and on debian I was happy with 2003-11-11. Are you sure
    >compiling the HEAD version solves the problem?
    >
    >Nobody uses mandrake here?


    I use Mandrake 9.2 (up to date with the latest patches) with a "self
    compiled" Ruby 1.8.1 with no problems, and I am messing around with a
    Tk application quite happily.

    [mike@ratdog mike]$ cat /etc/redhat-release
    Mandrake Linux release 9.2 (FiveStar) for i586
    [mike@ratdog mike]$ rpm -qa | grep '^tk-'
    tk-8.4.2-1mdk
    [mike@ratdog mike]$ ldd /usr/lib/libtk8.4.so
    libX11.so.6 => /usr/X11R6/lib/libX11.so.6 (0x400e2000)
    libdl.so.2 => /lib/libdl.so.2 (0x401c5000)
    libm.so.6 => /lib/i686/libm.so.6 (0x401c8000)
    libc.so.6 => /lib/i686/libc.so.6 (0x401eb000)
    /lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x80000000)

    Would there be any mileage in setting up something like Perl's smoke
    test system (see http://search.cpan.org/dist/Test-Smoke/FAQ and an
    example report from the archive
    http://www.nntp.perl.org/group/perl.daily-build.reports/13325)?

    Mike
    --
    | The "`Stok' disclaimers" apply.
    http://www.stok.co.uk/~mike/ | GPG PGP Key 1024D/059913DA
    | Fingerprint 0570 71CD 6790 7C28 3D60
    http://www.exegenix.com/ | 75D2 9EC4 C1C0 0599 13DA
    Mike Stok, Jan 20, 2004
    #11
  12. Ferenc Engard

    Guest

    Hi,

    At Tue, 20 Jan 2004 17:56:01 +0900,
    Ferenc Engard wrote:
    > Mandrake uses many dist-specific patches to libc. Cannot be the
    > problem connected with one of these patches?


    As for possibility, yes. But I don't know what patches there
    are.

    --
    Nobu Nakada
    , Jan 20, 2004
    #12
  13. On Wed, 21 Jan 2004, Andre Nathan wrote:

    >Ferenc Engard said:
    >> As there were no other suggestions, I try to do my first ruby
    >> compiling... :((
    >>
    >> Mandrake uses many dist-specific patches to libc. Cannot be the
    >> problem connected with one of these patches?

    >
    >Mandrake has a ruby-tk package. Did you install this one? Also, the
    >ruby rpm is not compiled with pthreads enabled (at least the one from
    >rpmfind.net). You could try editing the spec file and re-create the
    >rpm.


    Sorry, I looked on my debian box. On mdk, the ruby and the libtk do
    not depend on pthreads.

    So, this cannot be the problem. :-(((

    We use those packages, and my brother tried compile from the latest
    sources which mdk provides. Still crashes...

    The program crashes after I start to iterate through on a
    DBI::statementHandle with 2-3000 rows, but not always the same place.
    Sometimes during the iteration (searching, anyway), sometimes after
    it. I suspect to the GC, too, as many objects are created during this
    process.

    How can I get more debug info, which I can forward to you?

    Ferenc
    Ferenc Engard, Jan 20, 2004
    #13
  14. On Tue, 20 Jan 2004, Mike Stok wrote:

    >In article <>,
    >Ferenc Engard <> wrote:
    >>Does it affect multithreading (i.e., tk)?
    >>
    >>Anyway, it seems that the problem exists only on mandrake, even with
    >>newer ruby than on my debian box. The latest one was tried is
    >>2003-12-27, and on debian I was happy with 2003-11-11. Are you sure
    >>compiling the HEAD version solves the problem?
    >>
    >>Nobody uses mandrake here?

    >
    >I use Mandrake 9.2 (up to date with the latest patches) with a "self
    >compiled" Ruby 1.8.1 with no problems, and I am messing around with a
    >Tk application quite happily.
    >
    >[mike@ratdog mike]$ cat /etc/redhat-release
    >Mandrake Linux release 9.2 (FiveStar) for i586
    >[mike@ratdog mike]$ rpm -qa | grep '^tk-'
    >tk-8.4.2-1mdk


    Mine:

    ruby-1.8.1-1mdk (2004-01-07)
    tk-8.4.5-2mdk (2003-11-25)

    Home-made libmysql-ruby, the source seems to be 2.4.5, 2003-08-09

    I also use tktable and tix.

    Ferenc
    Ferenc Engard, Jan 20, 2004
    #14
  15. > > > > Here are the backtraces (sorry about the long mail):
    > > >
    > > > All seem related with GC. I guess it might be fixed in CVS
    > > > HEAD, or disapper by configuring with --disable-pthread.

    > >
    > > Does it affect multithreading (i.e., tk)?

    >
    > It should have worked before --enable-pthread was introduced.
    >
    > > Anyway, it seems that the problem exists only on mandrake, even with
    > > newer ruby than on my debian box. The latest one was tried is
    > > 2003-12-27, and on debian I was happy with 2003-11-11. Are you sure
    > > compiling the HEAD version solves the problem?

    >
    > Though I'm not sure, there are some fixes which are not
    > backported to 1.8 yet.


    Compiling from the yesterday's snapshot (with mdk patches) do not
    produce these errors. Thank you very much for your help!

    Ferenc
    Ferenc Engard, Jan 20, 2004
    #15
    1. Advertising

Want to reply to this thread or ask your own question?

It takes just 2 minutes to sign up (and it's free!). Just click the sign up button to choose a username and then you can ask your own questions on the forum.
Similar Threads
  1. John

    Eclipse with Mandrake 9.1

    John, Sep 12, 2003, in forum: Java
    Replies:
    0
    Views:
    344
  2. Gordon Beaton

    Java install problem in linux mandrake

    Gordon Beaton, Oct 27, 2003, in forum: Java
    Replies:
    2
    Views:
    407
    Daniel Dyer
    Oct 28, 2003
  3. David
    Replies:
    4
    Views:
    506
  4. Clément
    Replies:
    0
    Views:
    294
    Clément
    Nov 22, 2003
  5. Clément
    Replies:
    2
    Views:
    322
    Rolf Magnus
    Nov 25, 2003
Loading...

Share This Page