I have no idea, and I don't know what mingw32 is and there is no directory
c:\mingw32
on my laptop here. And I don't think it's ever been installed on
this system, haven't done any W32 development for years.
I think we should declare victory and move on. :-)
On 10/24/2025 2:11 PM, John Ralls wrote:
Huh. I wonder where
sys._base_executable = 'c:\\mingw32/bin/python'
sys.base_prefix = 'D:\\a\\msys64\\mingw32'
came from then. It would be c:\gcdev64\msys2\mingw32 on my system or any other
set up with the script from gnucash-on-windows.
Regards,
John Ralls
On Oct 24, 2025, at 10:02 AM, Paul Kinzelman <[email protected]> wrote:
I don't seem to have ming (or w64) installed and it sounds like getting a stack
trace would be difficult.
But I installed the 2024-10-24 build and the crash does not happen (whereas it
was repeatable every time before) so it looks like that one works, and the
stack trace is now a moot point.
Thank you!
On 10/24/2025 10:39 AM, John Ralls wrote:
If you already have Mingw64 installed then use its gdb. Trying to use the one I
packaged is going to have conflicts with your installed Mingw.
There are symbols for GnuCash and the libraries we build (AQBanking, OFX,
Guile) but not the ones that Mingw provides.
But no, it’s not useful to get a stack trace if a recent nightly shows that the
problem is already fixed. Please try the nightly build.
_______________________________________________
gnucash-user mailing list
[email protected]
To update your subscription preferences or to unsubscribe:
https://lists.gnucash.org/mailman/listinfo/gnucash-user
-----
Please remember to CC this list on all your replies.
You can do this by using Reply-To-List or Reply-All.
