---------- Forwarded message ----------
From: Lyes Amazouz <[EMAIL PROTECTED]>
Date: May 8, 2008 6:14 PM
Subject: Re: [Libevent-users] how to compile under cygwin
To: Nick Mathewson <[EMAIL PROTECTED]>, Lyes Amazouz <[EMAIL PROTECTED]>,
libevent-users@monkey.org



On 5/8/08, Nick Mathewson <[EMAIL PROTECTED]> wrote:
>
> I haven't tried cygwin in a while, but it used to work fine.  To learn
> more about where the bug is here, it might help if you can get a stack
> trace (using gdb) to figure out where the segfault is occurring.
> Also, if you can send a very small example thing that reproduces the
> bug for you, that would help too.
>
> Finally, make sure you're using Libevent 1.4.3 (or wait for Libevent
> 1.4.4, which should come out in the next 48 hours): they should be way
> less buggy than many older versions.
>
> yrs,
> --
> Nick
>
Sorry, this message is to be before the rattachements:

Thanks for you quick reponse. I'll wait for 1.4.4. In the mean time, could
you please find
a complete GDB and STRACE logs (attached).

All the best
Lyes

1) GDB TRACE:

1.1) Start GDB:

$ gdb app/warcserver.exe
GNU gdb 6.8.0.20080328-cvs (cygwin-special)
Copyright (C) 2008 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html
>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "i686-pc-cygwin"...
(gdb) r -i 10.211.55.4 -p 7777 -x tmp
Starting program: /cygdrive/c/warc-tools-read-only/app/warcserver.exe -i
10.211.55.4 -p 7777 -x tmp
[New thread 532.0xa7c]
[New thread 532.0xf7c]
Starting the WARC Server ...

1.2) Send a request :

curl http://10.211.55.4:7777/WARC/0.17

1.3) Return to GDB:

[New thread 532.0x8c0]
     10 [main] warcserver 532 _cygtls::handle_exceptions: Exception:
STATUS_ACCESS_VIOLATION
    989 [main] warcserver 532 open_stackdumpfile: Dumping stack trace to
warcserver.exe.stackdump
210501 [main] warcserver 532 _cygtls::handle_exceptions: Exception:
STATUS_ACCESS_VIOLATION
211948 [main] warcserver 532 _cygtls::handle_exceptions: Error while
dumping state (probably corrupted stack)

Program received signal SIGSEGV, Segmentation fault.
0x61016583 in stack_info::walk () from /usr/bin/cygwin1.dll
(gdb) backtrace
#0  0x61016583 in stack_info::walk () from /usr/bin/cygwin1.dll
#1  0x7c859bb0 in OutputDebugStringA () from
/cygdrive/c/WINDOWS/system32/kernel32.dll
#2  0x40010006 in ?? ()
#3  0x00000000 in ?? ()
(gdb)

1.4) Please find attached the coredump (warcserver.exe.stackdump)


2) STRACE:

2.1) Launch the application with STRACE:

$ strace  ./app/warcserver.exe -i 10.211.55.4 -p 7777 -x tmp
&>warcserver.exe.strace

2398351 [main] warcserver 4044 _cygtls::handle_exceptions: Exception:
STATUS_ACCESS_VIOLATION
2567102 [main] warcserver 4044 open_stackdumpfile: Dumping stack trace to
warcserver.exe.stackdump
2756096 [main] warcserver 4044 _cygtls::handle_exceptions: Exception:
STATUS_ACCESS_VIOLATION
2758951 [main] warcserver 4044 _cygtls::handle_exceptions: Error while
dumping state (probably corrupted stack)

2.2) Please find attached the STRACE log (warcserver.exe.strace)


-- 
===========
  |   Lyes Amazouz
  |   USTHB, Algiers
===========



-- 
===========
  |   Lyes Amazouz
  |   USTHB, Algiers
===========
_______________________________________________
Libevent-users mailing list
Libevent-users@monkey.org
http://monkeymail.org/mailman/listinfo/libevent-users

Reply via email to