Re: debugging QT plugins, was: debugging ofx file import

2019-01-21 Thread Jack
On 2019.01.21 13:18, Thomas Baumgart wrote: On Montag, 21. Januar 2019 17:02:56 CET Jack wrote: > On 1/21/19 10:42 AM, Thomas Baumgart wrote: [] So it finds the new plugin four times while looking for metadata, but finds the system version twice, and still manages to load the system vers

Re: debugging QT plugins, was: debugging ofx file import

2019-01-21 Thread Thomas Baumgart
On Montag, 21. Januar 2019 17:02:56 CET Jack wrote: > On 1/21/19 10:42 AM, Thomas Baumgart wrote: > > On Sonntag, 20. Januar 2019 01:16:06 CET Jack wrote: > >> On 2019.01.14 14:37, Ralf Habacker wrote: > >>> Am 14.01.19 um 20:31 schrieb Jack: > > [...] > >> So it finds the new plugin four times w

Re: debugging QT plugins, was: debugging ofx file import

2019-01-21 Thread Jack
On 1/21/19 10:42 AM, Thomas Baumgart wrote: On Sonntag, 20. Januar 2019 01:16:06 CET Jack wrote: On 2019.01.14 14:37, Ralf Habacker wrote: Am 14.01.19 um 20:31 schrieb Jack: [...] So it finds the new plugin four times while looking for metadata, but finds the system version twice, and still m

Re: debugging QT plugins, was: debugging ofx file import

2019-01-21 Thread Thomas Baumgart
Jack, On Sonntag, 20. Januar 2019 01:16:06 CET Jack wrote: > On 2019.01.14 14:37, Ralf Habacker wrote: > > Am 14.01.19 um 20:31 schrieb Jack: [...] > So it finds the new plugin four times while looking for metadata, but > finds the system version twice, and still manages to load the system

debugging QT plugins, was: debugging ofx file import

2019-01-19 Thread Jack
On 2019.01.14 14:37, Ralf Habacker wrote: Am 14.01.19 um 20:31 schrieb Jack:  >> The patch from https://phabricator.kde.org/D16764 should help. Thanks Ralph, and I'll give it a try, but I had thought an IDE (QT-Creator in this case) would know where things are, since it insists on compiling t

Re: debugging ofx file import

2019-01-14 Thread Ralf Habacker
Am 14.01.19 um 20:31 schrieb Jack:  >> The patch from https://phabricator.kde.org/D16764 should help. > Thanks Ralph, and I'll give it a try, but I had thought an IDE > (QT-Creator in this case) would know where things are, since it > insists on compiling the whole project before starting to debug

Re: debugging ofx file import

2019-01-14 Thread Jack
On 1/14/19 1:46 PM, Ralf Habacker wrote: Am 14.01.19 um 19:21 schrieb Jack: Any suggestions to what I might be missing would be appreciated. Not really. I don't know why the debugger does not stop for you. It does for me here. Are you sure you use plugins that have been compiled with debug symb

Re: debugging ofx file import

2019-01-14 Thread Ralf Habacker
Am 14.01.19 um 19:21 schrieb Jack: >>> Any suggestions to what I might be missing would be appreciated. >> Not really. I don't know why the debugger does not stop for you. It >> does for me here. Are you sure you use plugins that have been >> compiled with debug symbols and support? Not that you us

Re: debugging ofx file import

2019-01-14 Thread Jack
On 1/14/19 1:08 PM, Thomas Baumgart wrote: Jack, On Sonntag, 13. Januar 2019 18:59:09 CET Jack wrote: I'm trying to debug an issue with importing an ofx file, about how the importer finds the right account, or doesn't find it. I'm using QT-Creator, and have set lots of breakpoints in multiple

Re: debugging ofx file import

2019-01-14 Thread Thomas Baumgart
Jack, On Sonntag, 13. Januar 2019 18:59:09 CET Jack wrote: > I'm trying to debug an issue with importing an ofx file, about how the > importer finds the right account, or doesn't find it. I'm using > QT-Creator, and have set lots of breakpoints in multiple files which > seem to be involved

debugging ofx file import

2019-01-13 Thread Jack
I'm trying to debug an issue with importing an ofx file, about how the importer finds the right account, or doesn't find it. I'm using QT-Creator, and have set lots of breakpoints in multiple files which seem to be involved, but in all cases, I can't seem to hit a breakpoint until the ofx