On 30.08.2012 00:13, Graeme Geldenhuys wrote:
> Signal received. Signal: SIGSEGV, Segmentation fault.
>
> #0 0040E1BB :0 SYSTEM_WAITFREE_FIXED$PMEMCHUNK_FIXED$POSCHUNK()
> #1 01FB8D3C :0 ??()
> #2 0040C51A :0 fpc_finalize()
> #3 0001 :0 ??()
> #4 0040AD2A :0 SYSTEM_TOBJECT_$__CLEANUPINST
On 29/08/12 23:23, Jonas Maebe wrote:
The first thing you can try is to compile with -gh, hoping that it
will abort in a place closer to the cause of the problem. -CRr is
also a very useful debugging switch.
Thanks for the detailed information. The bug is not fixed yet, but I did
eventually
On 30 Aug 2012, at 00:13, Graeme Geldenhuys wrote:
> ---
> Signal received. Signal: SIGSEGV, Segmentation fault.
>
> #0 0040E1BB :0 SYSTEM_WAITFREE_FIXED$PMEMCHUNK_FIXED$POSCHUNK()
> #1 01FB8D3C :0 ??()
> #2 0040C51A :0 fpc_finalize()
> #3 0001 :0 ??()
> #4 0
Hi,
I hope somebody knows more about GDB that I. I'm trying to debug an
error in one of our Master Maths projects. This error only occurs under
Windows, where it bombs out at random times (in a specific section of
our product) with a "Segmentation Fault" error. GDB pauses the program
at that
I would like to build FP IDE with debugger support, it's been a long time
since I did it (and it was on windows). I've built GDB plainly (simply
./configure), and I have all necessary libraries (python, expat, decnumber,
zlib) but upon linking the IDE I got undefined references to those
libraries.
I can't figure out how to make a case insensitive search in GDB. The GDB docs
only say that you can do the following but don't give much else or explain
regexp.
forward-search regexp
or
reverse-search regexp
These works fine for simple (case sensitive) searches but I tried quite few
varia
Hello
Can anybody tell me how i can build fpc 2.5.1 with gdb support. I have
ubuntu 10.10 with gdb 7.2 binary package installed , when i tried to
'make build' i got linker errors like:
(.text+0x142): undefined reference to `_Py_NoneStruct'
//usr/lib/libgdb.a(py-type.o): In function `typy_get_
Tobias Giesen wrote on Thu, 15 Jul 2010:
I inserted $D- at the top of a few hundred units, but the app still
has the exact same file size. Is the $D- compiler directive ignored?
No.
Shouldn't the symbols shrink?
The Mac OS X linker does not copy the DWARF debug information from the
origi
Hello,
I am still struggling with the Segmentation Fault that gdb produces
when loading my app's symbols on Mac OS X.
I inserted $D- at the top of a few hundred units, but the app still
has the exact same file size. Is the $D- compiler directive ignored?
Shouldn't the symbols shrink?
Cheers,
Tob
On 03 Mar 2010, at 16:02, Seth Grover wrote:
> How can I print the value of a var ansistring parameter in gdb with
> dwarf debugging information compiled in?
I believe this is a bug that was introduced with GDB 7.0 (I can reproduce it
with GDB 7.0). Can you try with GDB 6.8 instead? With GDB 6.
Given the following example:
program project1;
{$mode objfpc}{$H+}
procedure doit (var s : ansistring);
begin
s := s + ' ' + s;
end;
var
s : ansistring;
begin
s := 'test';
doit(s);
end.
When I com
Dimitrios Chr. Ioannidis schreef:
Hi,
Is the 32 bit gdb in
http://svn.freepascal.org/svn/fpcbuild/trunk/install/binw32 able to
debug reliably a 64 bit process ?
AFAIK you cannot use the 32 bits version.
You can download gdb for win64 from SF. A tested version (but not the latest
version)
Hi,
i have build a native ppcx64 in windows 7 64 bit. But i can't find a 64
bit version of GDB in
http://svn.freepascal.org/svn/fpcbuild/trunk/install/binw64.
Is the 32 bit gdb in
http://svn.freepascal.org/svn/fpcbuild/trunk/install/binw32 able to
debug reliably a 64 bit process ? Or i must
On 31 May 2008, at 11:56, Tobias Giesen wrote:
now that the Lazarus snapshots are including FPC 2.2.1 for OS X
(i386),
I am using this version. I had to add the -Cg- option because my old
assembly code is not compatible with PIC.
Unfortunately the debugger crashes with the following crash re
Hello,
now that the Lazarus snapshots are including FPC 2.2.1 for OS X (i386),
I am using this version. I had to add the -Cg- option because my old
assembly code is not compatible with PIC.
Unfortunately the debugger crashes with the following crash report. Is
there anything I can do to make it w
On 02 Mar 2007, at 08:56, m utku wrote:
I am using an unstable fpc version(2.1.1 -- snapshot from last
week). While debugging my specific project, GDB(6.4 - Debian Sarge)
seems to be wrong about the function locations so I cannot use
breakpoints.
Do line numbers work?
I'd guess that thi
Hi all,
I am using an unstable fpc version(2.1.1 -- snapshot from last week).
While debugging my specific project, GDB(6.4 - Debian Sarge) seems to be
wrong about the function locations so I cannot use breakpoints. I'd
guess that this is a fpc bug about generated debug symbols. Is this is a
k
17 matches
Mail list logo
