No debug symbols for libapache2-mod-php5

Bug #611305 reported by Kurt Huwig
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
php5 (Ubuntu)
Invalid
Low
Unassigned

Bug Description

Binary package hint: php5

I cannot install the debug symbols which blocks bug #602689

apt-get install libapache2-mod-php5-dbgsym
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
  libapache2-mod-php5-dbgsym: Depends: libapache2-mod-php5 (= 5.3.2-1ubuntu4) but 5.3.2-1ubuntu4.2 is to be installed
E: Broken packages

If I force the installation, the symbols do not match the binary.

Changed in php5 (Ubuntu):
status: New → Invalid
Revision history for this message
Clint Byrum (clint-fewbar) wrote :

Hi Kurt, thanks for taking the time to create this bug report and help make Ubuntu better!

The debug symbols for libapache2-mod-php5 are in php5-dbg.

If there is still an issue with those debug symbols, please re-open the bug with more information, or open a new case with details.

Revision history for this message
Kurt Huwig (k-huwig) wrote :

As written in Bug #611316, the debug symbols for

/build/buildd/php5-5.3.2/ext/mssql/php_mssql.c

are off by 32 lines, according to the disassembly of a core dump.

Changed in php5 (Ubuntu):
status: Invalid → New
Revision history for this message
Mathias Gug (mathiaz) wrote :

Marking this bug invalid. If there is an issue with debug symbols, please open a new bug.

Changed in php5 (Ubuntu):
status: New → Invalid
importance: Undecided → Low
Revision history for this message
Clint Byrum (clint-fewbar) wrote :

Are you sure the symbols are inaccurate?

The patches that affect php_mssql.c just happen to add 32 lines of actual code...

So maybe you hadn't patched the files yet?

I tested today building on a clean maverick system and the debug symbols were in fact accurate, *after* the patches were applied.

Revision history for this message
Kurt Huwig (k-huwig) wrote :

Ah, sorry for the noise. I just did an "apt-get source" and did not apply the patches.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.