On May 20, 2014, at 2:56 AM, Campbell Barton <[email protected]> wrote:
> Recently I was writing a CPython module, in QtCreator and wasn't able > to debug it. > > Note that I would imagine this applies to any C-Extension, where you > don't directly execute the resulting library. > > The issue I ran into, is QtCreator wont allow the debugger to start > because it can tell there are no debug symbols in `/usr/bin/python`. That should only be a warning that still allows proceeding to debug. > However when using gdb I was able to run python and add breakpoints > into my C extension without any troubles. > > Is this a known issue or is there some way to tell QtCreator to ignore > if the binary has no debug syms? Options > Debugger > Warn when debugging “release” builds Br, Eike -- Eike Ziller, Senior Software Engineer - Digia, Qt Digia Germany GmbH, Rudower Chaussee 13, D-12489 Berlin Geschäftsführer: Mika Pälsi, Juha Varelius, Anja Wasenius Sitz der Gesellschaft: Berlin. Registergericht: Amtsgericht Charlottenburg, HRB 144331 B _______________________________________________ Qt-creator mailing list [email protected] http://lists.qt-project.org/mailman/listinfo/qt-creator
