NYCPHP Meetup

NYPHP.org

[nycphp-talk] PEAR Error Message

Baer, Jon jbaer at VillageVoice.com
Thu Oct 12 14:51:31 EDT 2006


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Were you looking for where the call was failing?  

I normally append that before the call to pinpoint where the function
was called, but im sure there is a debug level you can set for PEAR to
get more.

As Tim points out DB_DataObject::debugLevel(5); should definatley work.

APD is great to use (if you can compile/install it) though for debugging
all around .. http://pecl.php.net/package/apd

- - Jon

- -----Original Message-----
From: talk-bounces at lists.nyphp.org [mailto:talk-bounces at lists.nyphp.org]
On Behalf Of Phil Duffy
Sent: Thursday, October 12, 2006 2:41 PM
To: 'NYPHP Talk'
Subject: Re: [nycphp-talk] PEAR Error Message

Jon,

I received this as a response to my PEAR Error query.  I am sorry, but I
can't comprehend it.

Phil

> -----Original Message-----
> From: talk-bounces at lists.nyphp.org 
> [mailto:talk-bounces at lists.nyphp.org]
> On Behalf Of Baer, Jon
> Sent: Thursday, October 12, 2006 1:25 PM
> To: NYPHP Talk
> Subject: Re: [nycphp-talk] PEAR Error Message
> 
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> Is your signature call the same (or can you sed it out + append), you 
> can try appending something like
> 
> echo __FILE__ .':' . __LINE__;
> 
> Before the call.
> 
> - - Jon
> 
> - -----Original Message-----
> From: talk-bounces at lists.nyphp.org 
> [mailto:talk-bounces at lists.nyphp.org]
> On Behalf Of Phil Duffy
> Sent: Thursday, October 12, 2006 11:31 AM
> To: talk at lists.nyphp.org
> Subject: [nycphp-talk] PEAR Error Message
> 
> I have received the following PEAR error message, but can't interpret 
> it because there are many places where I am using a 'get':
> 
> MESSAGE: DB_DataObject Error: No Value specified for get
> TYPE: PEAR
> DEBUG INFO:
> CODE: -1
> 
> I have also tried bracketing the error, but that has not been helpful 
> to this point.
> 
> I recognize the Code = -1 as a failure signal, but the challenge is 
> that there is no debug information accompanying it.  The framework 
> (Seagull) log gives no indication of an error.  Have I failed to set 
> an appropriate parameter to allow Debug Info to display, does PEAR 
> have a unique log I am not seeing, or is there another way to 
> investigate this error?
> 
> Many thanks for your help.
> 
> Phil Duffy
> 
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.3 (MingW32)
> 
> iD8DBQFFLohl99e5DI8C/rsRAlukAJ9gMI8K1dBE9bd5jrs36t+zK7EY6QCgzRzE
> sMze1dvJH0xA49Y+TM99v5w=
> =Xr3V
> -----END PGP SIGNATURE-----
> _______________________________________________
> New York PHP Community Talk Mailing List 
> http://lists.nyphp.org/mailman/listinfo/talk
> 
> NYPHPCon 2006 Presentations Online
> http://www.nyphpcon.com
> 
> Show Your Participation in New York PHP 
> http://www.nyphp.org/show_participation.php




_______________________________________________
New York PHP Community Talk Mailing List
http://lists.nyphp.org/mailman/listinfo/talk

NYPHPCon 2006 Presentations Online
http://www.nyphpcon.com

Show Your Participation in New York PHP
http://www.nyphp.org/show_participation.php
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (MingW32)

iD8DBQFFLo6z99e5DI8C/rsRAsh7AKCMN1yarlgyW0fOQGG7O2CTKtka4ACfRTaE
v0ijacGvePN1nmj0stHdXzo=
=lKJo
-----END PGP SIGNATURE-----



More information about the talk mailing list