Hi Mark, If you're getting crashes without an update to the ~/.purple/Pidgin.RPT file and you want to get a backtrace, then you'll want to run Pidgin through gdb: https://developer.pidgin.im/wiki/GetABacktrace#TheEasyWay
Before you do that however, it'll be easier to get a debug log out of Pidgin https://developer.pidgin.im/wiki/TipsForBugReports#ObtainingaDebugLog There might be enough info in the debug log that running through gdb isn't needed, so definitely do this as a "step one." Would be interested to see what the backtrace/debug log shows though once you can grab it. :) Cheers, Eion On Tue, 3 Jul 2018 at 18:34, Mark Gillespie <[email protected]> wrote: > (sorry for new post, can't figure out how to reply, it's not obvious..) > > I am running 2.12.0, as the latest build still isn't released for Windows. > > I have installed the pdb debug as part of the install, however no crash > RPT file is created in the .purple directory (or anywhere else). It's > crashing in a Microsoft low level library. > > It's driving my nuts, as it many times a day. It's when monitor count and > resolution changes (when I dock or undock my laptop to my base station with > multiple monitors connected) > _______________________________________________ > [email protected] mailing list > Want to unsubscribe? Use this link: > https://pidgin.im/cgi-bin/mailman/listinfo/support
_______________________________________________ [email protected] mailing list Want to unsubscribe? Use this link: https://pidgin.im/cgi-bin/mailman/listinfo/support
