Here are the results of running relayd in debug mode, attached to pid of pfe
child:

pwd: /usr/src/usr.sbin/relayd

$ sudo gdb ./relayd
GNU gdb 6.3
Copyright 2004 Free Software Foundation, Inc.
GDB is free software, covered by
the GNU General Public License, and you are
welcome to change it and/or
distribute copies of it under certain conditions.
Type "show copying" to see
the conditions.
There is absolutely no warranty for GDB.  Type "show
warranty" for details.
This GDB was configured as
"amd64-unknown-openbsd5.3"...
(gdb) attach 28300
Attaching to program:
/usr/src/usr.sbin/relayd/relayd, process 28300
Loaded symbols for
/usr/src/usr.sbin/relayd/relayd
Reading symbols from
/usr/lib/libevent.so.3.1...done.
Loaded symbols for /usr/lib/libevent.so.3.1
Reading symbols from /usr/lib/libssl.so.19.0...done.
Loaded symbols for
/usr/lib/libssl.so.19.0
Reading symbols from
/usr/lib/libcrypto.so.22.0...done.
Loaded symbols for
/usr/lib/libcrypto.so.22.0
Reading symbols from
/usr/lib/libutil.so.11.4...done.
Loaded symbols for /usr/lib/libutil.so.11.4
Reading symbols from /usr/lib/libc.so.66.2...done.
Loaded symbols for
/usr/lib/libc.so.66.2
Reading symbols from /usr/libexec/ld.so...done.
Loaded
symbols for /usr/libexec/ld.so
[Switching to thread 1028300]
0x00001c765263481a in kevent () at <stdin>:2
2       <stdin>: No such
file or directory.
        in <stdin>
Current language:  auto;
currently asm
(gdb) continue
Continuing.
Program exited normally.
(gdb) 
The
program is not being run.
(gdb) 
The program is not being run.
(gdb) 
The
program is not being run.
(gdb) 
The program is not being run.
(gdb) 
The
program is not being run.
(gdb) 
The program is not being run.
(gdb) 
The
program is not being run.
(gdb) 
The program is not being run.
(gdb) 
The
program is not being run.
(gdb) 
The program is not being run.
(gdb) 
The
program is not being run.
(gdb) 
The program is not being run.
(gdb) 
The
program is not being run.
(gdb) 
The program is not being run.
(gdb) 
The
program is not being run.
(gdb) 
The program is not being run.
(gdb) 
The
program is not being run.
(gdb) 
The program is not being run.
(gdb) 
The
program is not being run.
(gdb) 
The program is not being run.
(gdb) 


But
the daemon relayd crashed.

Bogdan



________________________________
 From:
Stuart Henderson <s...@spacehopper.org>
To: Bogdan Andu <bo...@yahoo.com> 
Cc:
"misc@openbsd.org" <misc@openbsd.org> 
Sent: Wednesday, August 21, 2013 6:06
PM
Subject: Re: relayd crash
 

On 2013/08/21 06:32, Bogdan Andu wrote:
>
[Switching to thread 1027726]
> 0x0000029e250da81a in kevent () at <stdin>:2
>
2       <stdin>: No such file or directory.
>         in <stdin>
>
Current language:  auto; currently asm
> (gdb)

oh, I forgot, you will need
to "continue" here ;)

> 
> launched qualys scan and now waiting for crash to
occur - will take 2
> hours.
> 
> Unfortunately the relayd patch branch failed
with the same error, and
> that is why I tried relayd -current
> 
> I'll come
back with crash results
>
━━━━━━━━━━━━━━━━━━━━━━━━━â”
â”â”â”â”â”â”â”â”â”â”â”â”â”â”â”â”â”â”â”â”â”â”â”â”â”â
”â”â”â”â”â”â”â”â”â”â”â”â”â”â”â”â”â”â”â”
> From: Stuart
Henderson <s...@spacehopper.org>
> To: misc@openbsd.org
> Sent: Wednesday,
August 21, 2013 3:51 PM
> Subject: Re: relayd crash
> 
> On 2013-08-21, Bogdan
Andu <bo...@yahoo.com> wrote:
> > I tried relayd -current and crashed with the
error:
> > pwd:
> > /usr/src/usr.sbin/relayd
> >
> > $ sudo ./relayd -f
/etc/relayd.conf -d
> > ..... A LOT
> > OF LOGS ................
> > relay
www_ssl, session 1368 (1 active), 0,
> > 64.39.111.90 -> :0, SSL accept error
> > relay www_ssl, session 1369 (1 active),
> > 0, 64.39.111.90 ->
127.0.0.1:8080, done
> > pfe exiting, pid 8360
> > lost child:
> > relay
terminated; signal 11
> > hce exiting, pid 18726
> > parent terminating, pid
>
> 2704
> 
> Build it with debug symbols (make clean, make DEBUG=-g install)
>
and re-run it, then you can attach gdb to the pfe process (use ps
> to find
the correct pid and 'gdb /usr/sbin/relayd' and 'attach <pid>'.
> Now when you
trigger the crash you should be able to get a backtrace.

Reply via email to