John Ehresman added the comment:
I just ran into this again when I installed 2.7.10 -- evidently I had patched
my local installation and forgot about it. This is very important to anyone
who tries to use the Visual Studio C debugger to debug extension modules.
--
nosy: +jpe
Changes by Mark Lawrence breamore...@yahoo.co.uk:
--
nosy: +steve.dower
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue4214
___
___
Changes by Steve Dower steve.do...@microsoft.com:
--
assignee: tarek - steve.dower
resolution: - fixed
stage: - resolved
status: open - closed
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue4214
Roundup Robot added the comment:
New changeset 418095f0d711 by Steve Dower in branch '2.7':
Issue #4214: Remove ineffectual /pdb:none option from msvc9compiler.py
https://hg.python.org/cpython/rev/418095f0d711
New changeset 7c322c296a3b by Steve Dower in branch '3.4':
Issue #4214: Remove
Mark Lawrence added the comment:
Patch is against default. The entire distutils test suite ran okay. Would
someone like to try this in the real world please.
--
components: -Distutils2
keywords: +patch
nosy: +BreamoreBoy, dstufft
versions: +Python 3.4, Python 3.5 -3rd party, Python
Éric Araujo mer...@netwok.org added the comment:
Thanks for explaining. Is someone willing to add a test in test_msvc9compiler?
--
nosy: +loewis
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue4214
Martin v. Löwis mar...@v.loewis.de added the comment:
/pdb:None initially did *not* mean no debug information, but no pdb file,
see
http://msdn.microsoft.com/en-us/library/aa278542(VS.60).aspx
Debug information would be embedded to the DLL.
Later versions of the VS documentation fail to
Robin Dunn ro...@alldunn.com added the comment:
No, MSVC does not behave that way any longer. Now it simply creates a file
named None, so I expect that the newer versions simply do not support writing
the old-style debug info written to the DLL or EXE. If a setup script creates
more than one
Martin v. Löwis mar...@v.loewis.de added the comment:
Ah ok, then removing the option sounds fine to me (not for 2.6, though).
--
versions: -Python 2.6
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue4214
Amaury Forgeot d'Arc amaur...@gmail.com added the comment:
A .pdb is the program database that contain debug info, i.e. the mapping
between assembler positions and source lines, the description of data
structures, and other things that are necessary to debug a program.
--
Éric Araujo mer...@netwok.org added the comment:
What are pdb files, by the way?
--
components: +Distutils2
nosy: +eric.araujo
versions: +3rd party, Python 3.2 -Python 2.6, Python 3.0
___
Python tracker rep...@bugs.python.org
Tarek Ziadé ziade.ta...@gmail.com added the comment:
Since I am unfamiliar with MSVC, I will need to digg on this, so if
anyone can help on this : any idea on what would be the proper fix and
why ?
--
versions: +Python 2.7, Python 3.0, Python 3.1
___
Changes by Akira Kitada akit...@gmail.com:
--
assignee: - tarek
components: +Windows
nosy: +tarek
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue4214
___
New submission from Robin Dunn [EMAIL PROTECTED]:
It looks like part of r59290 resulted in /pdb:None always being part of
the ldflags_shared_debug list. This means that there will be no debug
info stored for extensions built in debug mode, which kinda negates the
purpose of doing a debug build.
Amaury Forgeot d'Arc [EMAIL PROTECTED] added the comment:
Furthermore, /PDB:None is no more supported by VC2008 express.
You end up with files named None...
--
nosy: +amaury.forgeotdarc
___
Python tracker [EMAIL PROTECTED]
15 matches
Mail list logo
