On 19 Dec 2008, at 09:48, Werner Bochtler wrote:
Andrew Brunner schrieb:
Thanks for that tip! So running under GDB I get the following
info...
This GDB was configured as "x86_64-linux-gnu"... (gdb) run
shared library problem and linux 64 bit -> maybe this problem is
related
to FPC bug
Andrew Brunner schrieb:
> Thanks for that tip! So running under GDB I get the following info...
>
> This GDB was configured as "x86_64-linux-gnu"... (gdb) run
shared library problem and linux 64 bit -> maybe this problem is related
to FPC bug reports 11931 / 12265 (jump table problem).
Werner
On Thu, Dec 18, 2008 at 2:04 AM, Michael Van Canneyt
wrote:
> Are you using threads ?
>
> Michael.
Hi Michael,
Not in the library project. Although I do plan on having threads in
the Main Application. Many pooled threads will be running in the main
application.
Just the "application" thread
On Wed, 17 Dec 2008, Andrew Brunner wrote:
> Thanks for that tip! So running under GDB I get the following info...
>
> This GDB was configured as "x86_64-linux-gnu"...
> (gdb) run
>
> Starting program: /mnt/Raid/Developer/Source/Lazarus/Test/TestApplication
> [Thread debugging using libthread
Thanks for that tip! So running under GDB I get the following info...
This GDB was configured as "x86_64-linux-gnu"...
(gdb) run
Starting program: /mnt/Raid/Developer/Source/Lazarus/Test/TestApplication
[Thread debugging using libthread_db enabled]
[New Thread 0x7f9e79102770 (LWP 7388)]
[WARNING
On 17 Dec 2008, at 02:55, Andrew Brunner wrote:
On Tue, Dec 16, 2008 at 3:29 PM, Jonas Maebe > wrote:
In what code does it crash? Inside unloadlibrary, or (shortly)
afterwards?
What is the backtrace at the point of the crash?
It blows out right during the DynLibs.UnloadLibrary(FLibHandle)
Read this to create a backtrace:
http://wiki.lazarus.freepascal.org/Creating_a_Backtrace_with_GDB
--
Felipe Monteiro de Carvalho
___
fpc-pascal maillist - fpc-pascal@lists.freepascal.org
http://lists.freepascal.org/mailman/listinfo/fpc-pascal
On Tue, Dec 16, 2008 at 3:29 PM, Jonas Maebe wrote:
> In what code does it crash? Inside unloadlibrary, or (shortly) afterwards?
> What is the backtrace at the point of the crash?
It blows out right during the DynLibs.UnloadLibrary(FLibHandle)
There is only a read access violation that is raise
On 16 Dec 2008, at 13:58, Andrew Brunner wrote:
I've been experiencing problems with SOs under Linux and am trying to
develop a "Plugin" system for my Server I'm porting to Lazarus. I'm
confident can get these Plug-ins to Load and Operate just fine at
least in (Ubuntu).
I can't however, Unloa
I've been experiencing problems with SOs under Linux and am trying to
develop a "Plugin" system for my Server I'm porting to Lazarus. I'm
confident can get these Plug-ins to Load and Operate just fine at
least in (Ubuntu).
I can't however, Unload them. I want to be able to use the
DynLibs.Unload
10 matches
Mail list logo