Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.forth > #25887
| From | Bernd Paysan <bernd.paysan@gmx.de> |
|---|---|
| Newsgroups | comp.lang.forth |
| Subject | Re: gForth and unix/pthread.fs |
| Date | 2013-09-21 15:55 +0200 |
| Organization | 1&1 Internet AG |
| Message-ID | <l1k8ge$q7h$1@online.de> (permalink) |
| References | (4 earlier) <l1hlir$kfk$1@online.de> <d2aaa163-6953-44b1-a862-60e5b04194b8@googlegroups.com> <l1hvcu$15u$1@online.de> <l1hvqe$1ti$1@online.de> <-ZGdnbpfIelX86DPnZ2dnUVZ_gidnZ2d@supernews.com> |
Andrew Haley wrote: > Bernd Paysan <bernd.paysan@gmx.de> wrote: >> This is a typical Ulrich Drepper: implement something in a way that can't >> possibly work, and then claim it is impossible to fix... > > C'mon Bernd, your English comprehension is better than that. He > didn't say mcheck was impossible to fix, he said it's impossible to > fix the technology underlying mcheck. And he did the underlying technology (which are the malloc hooks). So he did implement something that isn't possible to work in a multithreaded environmnent, and then is incapable of fixing it. Why the heck is it impossible to have thread-safe hooks for exception handling or other things like sanity checking? The whole exception stuff in malloc() is impossible to use reasonable. If something goes wrong in malloc() or free(), the default (thread-safe) behavior is to print a C backtrace and a memory map and terminate the program. For a VM, this is inadequate, because the C backtrace is meaningless, and terminating the program is a bad idea, too. We have our own exception handling. What I actually want is a hook for the exception reporting, which mcheck() doesn't really provide - it *also* turns on some more expensive sanity checking. I don't need or want that, the only thing I want is to take over when the normal code detects that there is something wrong. I would expect that only mcheck_pedantic() would install those sanity checks. And first of all, I would expect that a non-thread-safe function for otherwise thread-safe stuff (malloc is very explicitely stated to be thread- safe) would have a big warning label in the manpage. -- 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