El 24/11/21 a les 14:38, Luca Olivetti via lazarus ha escrit:
.
I suppose the message comes from some windows core dll and windbg can
display it, I don't know if and how gdb can (I'm not using fpdebug yet,
maybe it can?).
Well, call me stupid: the message is perfectly visible in the "Event
El 24/11/21 a les 14:38, Luca Olivetti via lazarus ha escrit:
El 24/11/21 a les 14:29, Martin Frb via lazarus ha escrit:
I don't know where that message came from, but is there a way to see
it while debugging the application under lazarus?
I would guess this is based on
El 24/11/21 a les 14:29, Martin Frb via lazarus ha escrit:
I don't know where that message came from, but is there a way to see
it while debugging the application under lazarus?
I would guess this is based on
On 24/11/2021 13:41, Luca Olivetti via lazarus wrote:
El 3/11/21 a les 15:56, Luca Olivetti via lazarus ha escrit:
A quick follow up: I used the wrong size when mallocing data (size of
the pointer variable instead of the size of the struct it pointed to,
d'oh!).
I found it by running the
El 3/11/21 a les 15:56, Luca Olivetti via lazarus ha escrit:
A quick follow up: I used the wrong size when mallocing data (size of
the pointer variable instead of the size of the struct it pointed to,
d'oh!).
I found it by running the program under windbg and there I saw a message
saying that
El 29/10/21 a les 12:48, Christo Crause ha escrit:
On Fri, Oct 29, 2021 at 10:41 AM Luca Olivetti via lazarus
mailto:lazarus@lists.lazarus-ide.org>>
wrote:
I now tested under windows 10 64 bits (the exe is 32 bits, the previous
test was under windows 7 32 bits), and here instead of
On Fri, Oct 29, 2021 at 10:41 AM Luca Olivetti via lazarus <
lazarus@lists.lazarus-ide.org> wrote:
>
> I now tested under windows 10 64 bits (the exe is 32 bits, the previous
> test was under windows 7 32 bits), and here instead of stopping once in
> ntdll!RtlpNtMakeTemporaryKey it stops twice:
El 28/10/21 a les 14:28, Christo Crause ha escrit:
On Thu, Oct 28, 2021 at 2:01 PM Luca Olivetti via lazarus
mailto:lazarus@lists.lazarus-ide.org>>
wrote:
77045AC4 cc int3
The Int3 instruction means break, so this is the expected behaviour. If
there is no
On 28/10/2021 14:28, Christo Crause via lazarus wrote:
On Thu, Oct 28, 2021 at 2:01 PM Luca Olivetti via lazarus
wrote:
77045AC4 cc int3
The Int3 instruction means break, so this is the expected behaviour.
If there is no debugger inserted break point for this
On Thu, Oct 28, 2021 at 2:01 PM Luca Olivetti via lazarus <
lazarus@lists.lazarus-ide.org> wrote:
>
> 77045AC4 cc int3
The Int3 instruction means break, so this is the expected behaviour. If
there is no debugger inserted break point for this location, it must be
compiled
I'm using a quite complex c dll (pascal headers here:
https://github.com/fluisgirardi./fpopen62541).
For logging purposes, this dll can call a function but it needs to
support varargs, so I wrote a simple c source
(https://github.com/fluisgirardi/fpopen62541/blob/main/pascallog/pascallog.c),
11 matches
Mail list logo
