StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

POPHP exception is caught, but error message still appears
primarykey
Id
8835004
data
AcceptedAnswerId
8835099
AnswerCount
4
ClosedDate
CommentCount
6
CommunityOwnedDate
CreationDate
2012-01-12T12:21:12.557
FavoriteCount
0
LastActivityDate
2018-04-30T18:52:36.973
LastEditDate
2018-04-30T18:52:36.973
LastEditorUserId
383764
OwnerUserId
518813
ParentId
0
PostTypeId
1
Score
4
ViewCount
2188
LastEditorDisplayName
text
Body
I use some code from the PHP manual to make an exception test, but I get some weird message. Here it is the code: <pre><code>function inverse($x) { if (!$x) { throw new Exception('Division by zero.'); } else return 1 / $x; } try { echo inverse(5) . "\n"; echo inverse(0) . "\n"; } catch (Exception $e) { echo 'Caught exception: ', $e->getMessage(), "\n"; } // Continue execution echo 'Hello World'; </code></pre> And here it is the output: <pre><code>0.2 ( ! ) Exception: Division by zero. in /var/www/OOPlearing/slash.php on line 10Call Stack#TimeMemoryFunctionLocation10.0002330188{main}( )../slash.php:020.0002330232inverse( $x = 0 )../slash.php:17Dump $_SERVER$_SERVER['HTTP_HOST'] =string 'localhost' (length=9)$_SERVER['SERVER_NAME'] =string 'localhost' (length=9)Dump $_GETVariables in local scope (#2)$x =int 0 Caught exception: Division by zero.Hello World </code></pre> It's strange that although the exception has been caught, the exception message is still on... Some of my local settings in php.ini: <pre><code>error_reporting = E_ALL & ~E_DEPRECATED display_errors =On display_startup_errors = Off log_errors = Off ...... html_errors = On </code></pre> My notebook: <pre><code>ubuntu11.04 mysql Ver 14.14 Distrib 5.1.54 PHP 5.3.5-1 </code></pre> Update(2012.1.16) It's the xdebug extension that resulted in such error outputs. The xdebug default shows stack traces on error conditions. For those who want to disable it can do below instruction: <pre><code>xdebug_disable();//put it on the header of your code,like cofig file. </code></pre> <a href="http://xdebug.org/docs/all_functions#xdebug_disable" rel="nofollow noreferrer" title="xdebug functions reference">more details</a>
Tags
<php><exception><error-handling>
Title
PHP exception is caught, but error message still appears
singulars
PostAcceptedAnswerId
1. PO
 singulars
 PostTypePostTypeId
 PTAnswer
PostParentId
1. This table or related slice is empty.
PostTypePostTypeId
1. PTQuestion
UserLastEditorUserId
1. USEmanuele Del Grande
UserOwnerUserId
1. USzhkzyth
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. PO
 singulars
 PostTypePostTypeId
 PTAnswer
2. PO
 singulars
 PostTypePostTypeId
 PTAnswer
3. PO
 singulars
 PostTypePostTypeId
 PTAnswer
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 POPHP exception is caught, but error message still appears
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
2. VO
 singulars
 PostPostId
 POPHP exception is caught, but error message still appears
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
3. VO
 singulars
 PostPostId
 POPHP exception is caught, but error message still appears
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
CommentsPostId

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.