[fpc-pascal] Possible fpdebug issue
Martin Frb
lazarus at mfriebe.de
Sun Apr 24 09:15:32 CEST 2022
Lazarus 2.2 or 2.3 ?
In 2.3 some work has been started to debug into dll...
Is there a way to reproduce this?
Also try:
lazarus.exe --debug-log=c:\logfile.txt
--debug-enable=DBG_EVENTS,DBG_VERBOSE,DBG_WARNINGS,DBG_ERRORS,DBG_VERBOSE_BRKPOINT,DBG_STATE,DBG_COMMAND_ECHO,DBG_DATA_MONITORS,DBG_LOCATION_INFO,DBG_BREAKPOINTS,DBG_FPDEBUG_VERBOSE,FPDBG_BREAKPOINT_ERRORS,FPDBG_BREAKPOINTS,FPDBG_COMMANDS,FPDBG_THREADS,FPDBG_QUEUE,FPDEBUG_THREAD_CHECK,FPDBG_WINDOWS
I am away for some days, so replies may take some time.
On 24/04/2022 02:15, Thomas Kurz via fpc-pascal wrote:
> Dear all,
>
> I'm not sure whether or not this is an issue with fpdebug, so I'd like to describe it here first:
>
> I have a main program (Win32 GUI running on Win 8.1) which loads and unloads a DLL dynamically. I know that fpdebug is currently not able to debug DLLs, but imho I don't do so, but the issue might be related.
>
> The program runs fine when being run without debugger or when using GDB. However, a crash occurs when fpdebug is active and the call to "FreeLibrary" is made. The error is:
>
> Project raised exception class 'External: Unknown exception code $E0465043'. At address 76EB56E8.
>
> The DLL is my own and I tried to debug the Finalization section with GDB, but I cannot find an issue there. So imho unloading the DLL should not cause any trouble. As I said, I'm not trying to actually step into the DLL; I'm only using fpdebug in the main program and trying to step over the "FreeLibrary" line.
>
> Kind regards,
> Thomas
>
> _______________________________________________
> fpc-pascal maillist - fpc-pascal at lists.freepascal.org
> https://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-pascal
More information about the fpc-pascal
mailing list