Thanks for the bug.

Roman Lacko takes care of PySide Windows packaging. He apparently hasn't
registered to our Bugzilla yet--I'll request him to do that and then move the
bug over to him.

I'm changing the priority to P4. Provide debug packages for windows requires a
huge effort because you need to have all dependencies compiled as debug or you
will have random crashes due to the use of two different msvcrt libraries in
the same process, so if the developer want to debug on Windows I think he's
capable of doing it by yourself.

I agree, that building PySide and all dependencies in debug is a hard work.

But not always debug build is required for debugging. In this bug report I
meant to build PySide in release, but with debugging symbols. To do so on
Windows I changed CMakeLists.txt and added 
  set(CMAKE_BUILD_TYPE RelWithDebInfo)
to build configuration. So now I have *.pdb files for PySide dll's and at least
can see call stack when something crashes.

(In reply to comment #3)
> I agree, that building PySide and all dependencies in debug is a hard work.
> 
> But not always debug build is required for debugging. In this bug report I
> meant to build PySide in release, but with debugging symbols. To do so on
> Windows I changed CMakeLists.txt and added 
>   set(CMAKE_BUILD_TYPE RelWithDebInfo)
> to build configuration. So now I have *.pdb files for PySide dll's and at least
> can see call stack when something crashes.

You are right, this is better than no debug at all, you can contact Roman Lacko
and help him with this, I don't want to push more work to Roman, he's already
doing a great job with the windows distribution.

(In reply to comment #4)
> (In reply to comment #3)
> > I agree, that building PySide and all dependencies in debug is a hard work.
> > 
> > But not always debug build is required for debugging. In this bug report I
> > meant to build PySide in release, but with debugging symbols. To do so on
> > Windows I changed CMakeLists.txt and added 
> >   set(CMAKE_BUILD_TYPE RelWithDebInfo)
> > to build configuration. So now I have *.pdb files for PySide dll's and at least
> > can see call stack when something crashes.
> 
> You are right, this is better than no debug at all, you can contact Roman Lacko
> and help him with this, I don't want to push more work to Roman, he's already
> doing a great job with the windows distribution.

I'm off the project based on PySide, as soon as I'll be back working close to
PySide I'll try to contribute. One of the problems in build scripts for windows
is that they not published by Roman Lacko in any repository so developers can't
centrally contribute to they (actually I don't know what is the situation with
repository now, but I failed to found anything like it about two months ago).

(In reply to comment #5)
> (In reply to comment #4)
> > (In reply to comment #3)
> > > I agree, that building PySide and all dependencies in debug is a hard work.
> > > 
> > > But not always debug build is required for debugging. In this bug report I
> > > meant to build PySide in release, but with debugging symbols. To do so on
> > > Windows I changed CMakeLists.txt and added 
> > >   set(CMAKE_BUILD_TYPE RelWithDebInfo)
> > > to build configuration. So now I have *.pdb files for PySide dll's and at least
> > > can see call stack when something crashes.
> > 
> > You are right, this is better than no debug at all, you can contact Roman Lacko
> > and help him with this, I don't want to push more work to Roman, he's already
> > doing a great job with the windows distribution.
> 
> I'm off the project based on PySide, as soon as I'll be back working close to
> PySide I'll try to contribute. One of the problems in build scripts for windows
> is that they not published by Roman Lacko in any repository so developers can't
> centrally contribute to they (actually I don't know what is the situation with
> repository now, but I failed to found anything like it about two months ago).

Hi,
I promise I will upload the buildscipts to PySide repository ASAP. Until then I
will try to create and upload distribution with debug symbols.

(In reply to comment #6)
> (In reply to comment #5)
> > (In reply to comment #4)
> > > (In reply to comment #3)
> > > > I agree, that building PySide and all dependencies in debug is a hard work.
> > > > 
> > > > But not always debug build is required for debugging. In this bug report I
> > > > meant to build PySide in release, but with debugging symbols. To do so on
> > > > Windows I changed CMakeLists.txt and added 
> > > >   set(CMAKE_BUILD_TYPE RelWithDebInfo)
> > > > to build configuration. So now I have *.pdb files for PySide dll's and at least
> > > > can see call stack when something crashes.
> > > 
> > > You are right, this is better than no debug at all, you can contact Roman Lacko
> > > and help him with this, I don't want to push more work to Roman, he's already
> > > doing a great job with the windows distribution.
> > 
> > I'm off the project based on PySide, as soon as I'll be back working close to
> > PySide I'll try to contribute. One of the problems in build scripts for windows
> > is that they not published by Roman Lacko in any repository so developers can't
> > centrally contribute to they (actually I don't know what is the situation with
> > repository now, but I failed to found anything like it about two months ago).
> 
> Hi,
> I promise I will upload the buildscipts to PySide repository ASAP. Until then I
> will try to create and upload distribution with debug symbols.

Roman, big thanks to you for work that you are doing for PySide and it's
community!

Changing the status to WAITING, as this will be feasible only when the Qt and
Python developers provide debug versions for MSVC of their products otherwise
generate debug packages will be a pain.

Roman, if you agree we can mark this bug as WONTFIX, as I believe that there
will not exist debug versions of those packages (Qt and Python) for MSVC soon
causing this bug can stay here forever.

Hugo,

I suggest to provide debug symbols only for PySide libraries as I noted in
comment 3 and you agreed comment 4, that this would be better solution that no
debugging symbols at all.

(In reply to comment #9)
> Hugo,
> 
> I suggest to provide debug symbols only for PySide libraries as I noted in
> comment 3 and you agreed comment 4, that this would be better solution that no
> debugging symbols at all.

Right, I tried to use my memory about this bug report instead of reading all
comments... duh!

Changing the status to NEW.

PySide is now a Qt-addon and uses Qt Project's JIRA tool for tracking bugs.
Please verify that the bug is still valid and re-submit it in the address
below:

https://bugreports.qt-project.org/

Sorry for the inconvenience!