# tsrm_shutdown() and the CLI SAPI

- Thread: https://externals.io/message/23828
- Original archive: https://news-web.php.net/php.internals/23828
- Started by Frank M. Kromann on 2006-05-31T14:58:05+00:00
- Messages: 6
- Reply by email to internals@lists.php.net
- More for agents: search with https://externals.io/search.md?q={query} · JSON API at https://externals.io/api · documentation at https://externals.io/llms.txt

---

## #23828 — Frank M. Kromann — 2006-05-31T14:58:05+00:00

URL: https://externals.io/message/23828#23828

tsrm_shutdown() is already comented out in the CGI version, most likely as
a fix to the same kind of problem there. Perhaps enabling that again will
show the same kind of problems?

- Frank

> At the moment I'm seeing it with Tidy under 5_2.  Just about to get Tony
to 
> check.
> 
> ----- Original Message ----- 
> From: "Dmitry Stogov" <dmitry@zend.com>
> To: "'Steph Fox'" <steph@zend.com>; "'Xuefer'" <xuefer@gmail.com>;
"'Andi 
> Gutmans'" <andi@zend.com>
> Cc: "'internals'" <internals@lists.php.net>; "'Antony Dovgal'" 
> <antony@zend.com>
> Sent: Wednesday, May 31, 2006 2:55 PM
> Subject: RE: [PHP-DEV] tsrm_shutdown() and the CLI SAPI
> 
> 
> > […]
bugs.
> > […]
don't
> > […]
same
> > […]
am
> > […]
in
> > […]

---

## #23829 — Steph Fox — 2006-05-31T15:23:50+00:00

URL: https://externals.io/message/23828#23829 · In reply to: #23828

Hi Frank,

> tsrm_shutdown() is already comented out in the CGI version, most likely as
> a fix to the same kind of problem there. Perhaps enabling that again will
> show the same kind of problems?

Yes, it would, given the root cause - but would you really want to break the 
whole of PHP for an academic exercise?

The more interesting thing is that none of this happens under CLI debug. 
I've still no clue why.

I also think I've somehow corrupted something here with my debug lines, I'm 
crashing 'differently' now <sigh />.

- Steph

> - Frank

---

## #23840 — Andi Gutmans — 2006-06-01T04:25:56+00:00

URL: https://externals.io/message/23828#23840 · In reply to: #23829

At 08:23 AM 5/31/2006, Steph Fox wrote:
>Hi Frank,
>
> > […]
>
>Yes, it would, given the root cause - but would you really want to 
>break the whole of PHP for an academic exercise?

It's not really an academic exercise. If we know there's a bug 
someplace we should at least look into it and try and understand it. 
Then if we decide to remove the trsm_shutdown call for a good reason 
(circular dependency, blah blah blah) then we can do that and put a 
nice fat comment on why it's the right thing to do. But I do think 
it's benefical to try and understand what's happening.

Andi


>The more interesting thing is that none of this happens under CLI 
>debug. I've still no clue why.
>
>I also think I've somehow corrupted something here with my debug 
>lines, I'm crashing 'differently' now <sigh />.
>
>- Steph
>
> > […]

---

## #23842 — Steph Fox — 2006-06-01T04:50:43+00:00

URL: https://externals.io/message/23828#23842 · In reply to: #23840

> > […]
>
> It's not really an academic exercise. If we know there's a bug someplace 
> we should at least look into it and try and understand it.

Frank's referring to Zeev's three-years-ago decision to simply opt out of 
tsrm_shutdown() here... he's suggesting we revert it.

> Then if we decide to remove the trsm_shutdown call for a good reason 
> (circular dependency, blah blah blah) then we can do that and put a nice 
> fat comment on why it's the right thing to do. But I do think it's 
> benefical to try and understand what's happening.

Fine, but breaking working code while you're trying to understand what's 
happening is far from beneficial to our users. Can't we at least #0 it?

>
> Andi

---

## #23845 — Andi Gutmans — 2006-06-01T06:28:49+00:00

URL: https://externals.io/message/23828#23845 · In reply to: #23842

As we are not planning to release a new version within the next 
couple of weeks, I suggest before jumping to conclusions we take a look at it.

If you really need to comment out that line in the meanwhile that's OK with me.

Andi

At 09:50 PM 5/31/2006, Steph Fox wrote:
> > […]
>
>Frank's referring to Zeev's three-years-ago decision to simply opt 
>out of tsrm_shutdown() here... he's suggesting we revert it.
>
> > […]
>
>Fine, but breaking working code while you're trying to understand 
>what's happening is far from beneficial to our users. Can't we at least #0 it?
>
> > […]

---

## #23855 — Steph Fox — 2006-06-01T16:59:27+00:00

URL: https://externals.io/message/23828#23855 · In reply to: #23845

We were hoping to release ours...

----- Original Message ----- 
From: "Andi Gutmans" <andi@zend.com>
To: "Steph Fox" <steph@zend.com>; "Frank M. Kromann" <frank@kromann.info>
Cc: "'internals'" <internals@lists.php.net>; "'Antony Dovgal'" 
<antony@zend.com>; "Dmitry Stogov" <dmitry@zend.com>; "'Xuefer'" 
<xuefer@gmail.com>
Sent: Thursday, June 01, 2006 8:28 AM
Subject: Re: [PHP-DEV] tsrm_shutdown() and the CLI SAPI


> As we are not planning to release a new version within the next couple of 
> weeks, I suggest before jumping to conclusions we take a look at it.
>
> If you really need to comment out that line in the meanwhile that's OK 
> with me.
>
> Andi
>
> At 09:50 PM 5/31/2006, Steph Fox wrote:
> > […]
>
>
> __________ NOD32 1.1380 (20060125) Information __________
>
> This message was checked by NOD32 antivirus system.
> http://www.eset.com
