Opened 8 years ago

Closed 6 years ago

Last modified 43 years ago

#254 closed Bugs (Invalid)

Corruption of data when returning from function

Reported by: nobody Owned by: nobody
Priority: 5 Milestone:
Component: None Version: None
Keywords: Cc:

Description

Hi Y'all

I've come across an interesting corruption of data when
using the debugger 'step into' feature. The effect
doesn't occur when the function call in question is
'stepped over', so I'm certain it isn't the code, or
the debugger.

The function in question is handed an ID for a MySQL
database record by the ::main() PHP script. This
function then calls another function with this ID as a
parameter which in turn accesses the database and
returns the data relevant to the ID.

The data returned is a price for a component. It is
fetched correctly by the innermost function (eg 29.99),
and returned to the second level function as per usual
in function calls.

The second level function then returns the price to
::main(), but when the variable is examined in ::main()
it has suddenly been converted into '2005-01-03' or
another such date.

This, I'm guessing, is not the intended functionality
of the plugin or the debugger.

As I say, this doesn't occur when the function call in
::main() is stepped over, only when it is stepped into.

Is this a known bug, or is it something new?


Change History (3)

comment:1 Changed 6 years ago by scorphus

Logged In: YES 
user_id=987242
Originator: NO

I tried unsuccessfully to reproduce this bug by debugging the attached sample code with both DBG and XDebug.

I think it might be already fixed, but I'll have someone else to look and see if we can close it.

I'm also attaching a simple SQL script to create a sample table with three records in it.

Thanks.

PHPeclipse 1.2.0.CVS-current
Eclipse 3.2.2 build M20070212-1330
Sun Java 1.5.0_06
Debian Sid i686 GNU/Linux-2.6.18

File Added: 1154950_sample.php

comment:2 Changed 6 years ago by scorphus

Logged In: YES 
user_id=987242
Originator: NO

File Added: 1154950_sql_script.sql

comment:3 Changed 6 years ago by scorphus

  • Status changed from assigned to closed
Logged In: YES 
user_id=987242
Originator: NO

A couldn't reproduce this one, in anyway. I doubt that this ever was really an issue. So, it's getting closed as it contains few environment information and is too old.
Note: See TracTickets for help on using tickets.