On Wed, Jun 02, 2004 at 11:04:15AM -0400, Christopher Faylor wrote:
> On Wed, Jun 02, 2004 at 10:06:06AM +0200, Demmer, Thomas wrote:
> >(gdb) run
> >Starting program: /m/c/insi.exe
> >
> >Program received signal SIGSEGV, Segmentation fault.
> >0x77e75a3f in KERNEL32!IsBadWritePtr () from
> >/c/WI
cgf wrote:
>On Wed, Jun 02, 2004 at 10:06:06AM +0200, Demmer, Thomas wrote:
>>Hi list,
[...]
>>
>>Program received signal SIGSEGV, Segmentation fault.
>>0x77e75a3f in KERNEL32!IsBadWritePtr () from
>>/c/WINDOWS/system32/kernel32.dll
>>
>>This does not happen when compiled with -mno-cygwin.
>
>Just
On Wed, Jun 02, 2004 at 10:06:06AM +0200, Demmer, Thomas wrote:
>Hi list,
>I have encountered a strange situation that I can boil down to
>the attached test case. To reproduce the problem
>issue
>$ echo 123 > a.dat
>$ gcc -Wall -pedantic -o insi insi.c
>
>The program runs fine when run from the co
At 04:06 AM 6/2/2004, you wrote:
>Hi list,
>I have encountered a strange situation that I can boil down to
>the attached test case. To reproduce the problem
>issue
>$ echo 123 > a.dat
>$ gcc -Wall -pedantic -o insi insi.c
>
>The program runs fine when run from the command-line. Running
>within in
Hi list,
I have encountered a strange situation that I can boil down to
the attached test case. To reproduce the problem
issue
$ echo 123 > a.dat
$ gcc -Wall -pedantic -o insi insi.c
The program runs fine when run from the command-line. Running
within insight or gdb the sscanf dies with
(gdb) r
5 matches
Mail list logo