#2406 Tcl_OpenFileChannel trashes memory

obsolete: 8.4.3
closed-out-of-date
8
2006-03-10
2003-07-12
Zoran Vasiljevic
No

The Tcl_OpenFileChannel API call trashes memory
when feeded with NULL interp. The workaround was
to open the file using standard open() and then
do Tcl_MakeFileChannel() using the resulting OS handle.
This was observed on Linux, Solaris and Darwin. I havent
tested it on Windows.
Interestingly, Purify on Solaris can't pinpoint anything.
I assume the problem lies somewhere in the new path
management code.

Discussion

  • Don Porter
    Don Porter
    2003-10-02

    • priority: 5 --> 8
     
  • Logged In: YES
    user_id=75003

    Zoran, do you have some example code I could use to
    reproduce the smash ?

     
  • Logged In: YES
    user_id=75003

    Zoran, can you retest this with 8.4.7 and 8.5 ?

    Also, please try to reproduce with a regular core, a core
    with --enable-symbols=all, and one with --enable-symbols=symbols
    The latter provides us with symbols for a good stacktrace,
    but leaves mem debugging out of it, i.e. does not disturb
    the mem layout.

     
  • Don Porter
    Don Porter
    2006-03-10

    • status: open --> pending-out-of-date
     
  • Don Porter
    Don Porter
    2006-03-10

    Logged In: YES
    user_id=80530

    Is this bug still valid? A number
    of routines have been made more
    NULL interp tolerant recently.

    Marking Pending - Out of Date
    unless someone can demo it's
    still an issue for 8.4.13 or
    8.5a4.

     
  • Logged In: YES
    user_id=95086

    I tried to trigger it using the last cvs state for core-8-4-branch
    but was not able to. Seems to be that recent changes reg. NULL
    interp have solved the problem.
    I'm closing this one.

     
    • status: pending-out-of-date --> closed-out-of-date