Uwe Grauer wrote:
Maybe this helps?
Here is my debug window:
(from Lazarus, I assume?)
<-gdb-set env ALLUSERSPROFILE=C:\Documents and Settings\All Users>
^done
It seems your Lazarus version does set Environmental variables correctly?
<-data-evaluate-expression FPC_THREADVAR_RELOCATE_PROC>
^done,value="0x0"
In my case it doesn't find this prog, but I guess that is because my program isn't using threadvars.
*stopped,reason="signal-received",signal-name="SIGSEGV",signal-meaning="Segmentation
fault",thread-id="1",frame={addr="$004054c7",func="fpc_ansistr_incr_ref",args=[{name="S",value="$baadf00d"}],file="astrings.inc",line="119"}
fpc_ansistr_inc_ref is called with an invalid pointer ($baadf00d). This
indicates uninitialized memory usage. The behaviour of your program in such
cases can vary depending on how, where and when the app is started.
Open the Callstack debug window in Lazarus, so you get a stack trace. (or type
'bt' when ran from gdb console). It is important from where the routine is
called in order to trace the problem. (of course, one not only needs file names
+ line numbers, but also source code lines)
Regards,
Bram
_________________________________________________________________
To unsubscribe: mail [EMAIL PROTECTED] with
"unsubscribe" as the Subject
archives at http://www.lazarus.freepascal.org/mailarchives
