Shmuel Vagner wrote:
> My question: Is there a patch for this and how can I install it (does it
> involves building Cygwin from source or is there another simpler way)?
Patches to avoid the spurious SIGSEGV faults are already in CVS for both
Cygwin and gdb. But you'll have to build both of them
On 06 March 2006 17:25, Shmuel Vagner wrote:
> HI,
> I am using a SlickEdit IDE to compile and debug my projects.
> When debugging a new operator gdb reports a segmentation fault.
> I found this problem in the archives and the proposed solution is to
> ignore the fault and continue debugging.
> Un
HI,
I am using a SlickEdit IDE to compile and debug my projects.
When debugging a new operator gdb reports a segmentation fault.
I found this problem in the archives and the proposed solution is to
ignore the fault and continue debugging.
Unfortunately this is possible with gdb or ddd but not with
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Dierk Bolten on 2/3/2006 6:20 AM:
>
> when I run tree.exe on an example xml file inside bash it works fine, but
> when
> I start the program inside gdb (or ddd), gdb receives a sig fault
>
>
> Program received signal SIGSEGV, Segmenta
Hi!
While playing around with an example file of the libxml2 library (2.6.22-1), I
ran into problems using the gdb debugger (I used the ddd and insight front-end,
but the problem also comes up when invoking gdb (GNU gdb 6.3.50_2004-12-28-cvs
(cygwin-special)) directly). The example file (tree.c
5 matches
Mail list logo