Re: Memory corruption

2004-01-21 Thread Leopold Toetsch
Leopold Toetsch <[EMAIL PROTECTED]> wrote: > Steve Fink <[EMAIL PROTECTED]> wrote: >> It crashes on a memcpy inside compact_pool > Some remarks what I could find out: > - current COW copying of stacks is AFAIK borken - both "copies" of > one COWed stack share the same Buffer header I have now

Re: Memory corruption

2004-01-20 Thread Leopold Toetsch
Steve Fink <[EMAIL PROTECTED]> wrote: > Here's another obnoxious test case. [ ... ] > So, in case anyone is curious (hi leo!), attached is a 56KB (<9KB > gzipped) imc file. > It crashes on a memcpy inside compact_pool Some remarks what I could find out: - the damaged Buffer is in a pool of obje

[APPLIED (partially)] Re: Memory Corruption Bug

2002-03-29 Thread Melvin Smith
At 07:57 PM 3/29/2002 +0200, you wrote: >"Michel J Lambert" <[EMAIL PROTECTED]> wrote: > > > Attached is a .pasm file which causes some string data to be written into > > the middle of the string_pool->pool_buffer list of entries, such that when > > it tries to dereference foo in new_pmc_header, i

Re: Memory Corruption Bug

2002-03-29 Thread Peter Gibbs
"Michel J Lambert" <[EMAIL PROTECTED]> wrote: > Attached is a .pasm file which causes some string data to be written into > the middle of the string_pool->pool_buffer list of entries, such that when > it tries to dereference foo in new_pmc_header, it's pointing to garbage > memory. 0x20202020 for