Vulnerability Development mailing list archives
Re: IE/OSX bad memory access
From: KF <dotslash () snosoft com>
Date: Fri, 31 May 2002 00:15:34 -0400
Could this be a problem with XSLT? I noticed the web page is boasting new XSL stuff and is also linking to
http://www.w3.org/Style/XSL/ -KF J. Mallett wrote:
Here's a backtrace: [Switching to thread 7 (process 2937 thread 0x2403)] Program received signal EXC_BAD_ACCESS, Could not access memory. [Switching to process 2937 thread 0x2403] 0x0058b520 in ?? () (gdb) bt #0 0x0058b520 in ?? () #1 0x0058b4f4 in ?? () #2 0x0057c6c0 in ?? () #3 0x0057c2b8 in ?? () #4 0x0057c2ec in ?? () #5 0x006cbe70 in ?? () #6 0x00570be8 in ?? () #7 0x0056fb48 in ?? () #8 0x00698f24 in ?? () #9 0x005bc2a8 in ?? () #10 0x006a509c in ?? () #11 0x005c2084 in ?? () #12 0x005bff68 in ?? () #13 0x006f9bdc in ?? () #14 0x006e76bc in ?? () #15 0x00560ab0 in ?? () #16 0x00790424 in ?? () #17 0x004ca368 in ?? () #18 0x7027ae58 in CooperativeThread () #19 0x7002054c in _pthread_body ()(gdb)From when going to the url:http://segment7.net/main.html There you go.
Current thread:
- IE/OSX bad memory access J. Mallett (May 31)
- Re: IE/OSX bad memory access KF (May 31)