Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.forth > #25847
| From | Bernd Paysan <bernd.paysan@gmx.de> |
|---|---|
| Newsgroups | comp.lang.forth |
| Subject | Re: gForth and unix/pthread.fs |
| Date | 2013-09-20 19:14 +0200 |
| Organization | 1&1 Internet AG |
| Message-ID | <l1hvqe$1ti$1@online.de> (permalink) |
| References | (2 earlier) <l1g17c$m9g$1@online.de> <24d1514e-0155-4b43-a88d-bb274c855887@googlegroups.com> <l1hlir$kfk$1@online.de> <d2aaa163-6953-44b1-a862-60e5b04194b8@googlegroups.com> <l1hvcu$15u$1@online.de> |
Bernd Paysan wrote: > My impression is that glibc's memory management is not really thread-safe, > and that this causes severe problems. I've enabled malloc checks to get a > chance to print meaningful error messages in Forth, but that seems to > rather increase the number of potential problems... I've now disabled the use of mcheck(), and this seems to cure the problem. Please try. I've added mcheck() to make it possible to debug memory errors from within Forth (and getting a meaningful backtrace), but Ulrich Drepper defeats that idea... Ulrich Drepper's comment on this is: "mcheck does not work for multi-threaded code. It cannot possibly do. There is no way to fix this with the technology underlying mcheck." m( This is a typical Ulrich Drepper: implement something in a way that can't possibly work, and then claim it is impossible to fix... -- Bernd Paysan "If you want it done right, you have to do it yourself" http://bernd-paysan.de/
Back to comp.lang.forth | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
gForth and unix/pthread.fs voidvolker@gmail.com - 2013-09-16 00:43 -0700
Re: gForth and unix/pthread.fs anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2013-09-16 09:05 +0000
Re: gForth and unix/pthread.fs voidvolker@gmail.com - 2013-09-16 05:43 -0700
Re: gForth and unix/pthread.fs VoidVolker <voidvolker@gmail.com> - 2013-09-19 10:14 -0700
Re: gForth and unix/pthread.fs Bernd Paysan <bernd.paysan@gmx.de> - 2013-09-20 01:26 +0200
Re: gForth and unix/pthread.fs VoidVolker <voidvolker@gmail.com> - 2013-09-19 19:17 -0700
Re: gForth and unix/pthread.fs Bernd Paysan <bernd.paysan@gmx.de> - 2013-09-20 16:20 +0200
Re: gForth and unix/pthread.fs VoidVolker <voidvolker@gmail.com> - 2013-09-20 08:43 -0700
Re: gForth and unix/pthread.fs Bernd Paysan <bernd.paysan@gmx.de> - 2013-09-20 19:07 +0200
Re: gForth and unix/pthread.fs Bernd Paysan <bernd.paysan@gmx.de> - 2013-09-20 19:14 +0200
Re: gForth and unix/pthread.fs Andrew Haley <andrew29@littlepinkcloud.invalid> - 2013-09-21 05:02 -0500
Re: gForth and unix/pthread.fs Bernd Paysan <bernd.paysan@gmx.de> - 2013-09-21 15:55 +0200
Re: gForth and unix/pthread.fs Andrew Haley <andrew29@littlepinkcloud.invalid> - 2013-09-21 11:32 -0500
Re: gForth and unix/pthread.fs Bernd Paysan <bernd.paysan@gmx.de> - 2013-09-21 20:44 +0200
Re: gForth and unix/pthread.fs Andrew Haley <andrew29@littlepinkcloud.invalid> - 2013-09-22 05:03 -0500
Re: gForth and unix/pthread.fs Bernd Paysan <bernd.paysan@gmx.de> - 2013-09-22 21:18 +0200
Re: gForth and unix/pthread.fs VoidVolker <voidvolker@gmail.com> - 2013-09-21 11:41 -0700
Re: gForth and unix/pthread.fs Bernd Paysan <bernd.paysan@gmx.de> - 2013-09-21 21:18 +0200
Re: gForth and unix/pthread.fs VoidVolker <voidvolker@gmail.com> - 2013-09-21 13:55 -0700
Re: gForth and unix/pthread.fs Bernd Paysan <bernd.paysan@gmx.de> - 2013-09-21 23:40 +0200
Re: gForth and unix/pthread.fs albert@spenarnc.xs4all.nl (Albert van der Horst) - 2013-09-21 12:59 +0000
csiph-web