DragonFlyBSD

On Thu, Jun 08, 2006 at 08:01:46AM +0100, Mark Cullen wrote:

I got everything set up, switched hard disks, and everything seemed to
work alright except for Samba. I was seeing the same error as
http://leaf.dragonflybsd.org/mailarchive/users/2005-09/msg00247.html

I tried recompiling Samba with the -fno-stack-protector flag, as
mentioned in that thread, but that didn't seem to solve the issue (or I
did it wrong). Is anyone else still seeing this one?

I have a PDC running 1.4.4... If you can get me a coredump from Samba
build with debug symbols, I can try to trace it down. But without that,
it is quite hard.

Joerg

joerg@britannica.bec.de wrote:

On Thu, Jun 08, 2006 at 08:01:46AM +0100, Mark Cullen wrote:

I got everything set up, switched hard disks, and everything seemed to
work alright except for Samba. I was seeing the same error as
http://leaf.dragonflybsd.org/mailarchive/users/2005-09/msg00247.html

I tried recompiling Samba with the -fno-stack-protector flag, as
mentioned in that thread, but that didn't seem to solve the issue (or I
did it wrong). Is anyone else still seeing this one?

I have a PDC running 1.4.4... If you can get me a coredump from Samba
build with debug symbols, I can try to trace it down. But without that,
it is quite hard.

Joerg

How might I go about building it with debug symbols?

On Thu, Jun 08, 2006 at 04:33:44PM +0100, Mark Cullen wrote:

joerg@britannica.bec.de wrote:

I have a PDC running 1.4.4... If you can get me a coredump from Samba
build with debug symbols, I can try to trace it down. But without that,
it is quite hard.

Joerg

How might I go about building it with debug symbols?

Try adding
CFLAGS= -O2 -g
CXXFLAGS= -O2 -g

to /etc/mk.conf. The smbd binary in the work directory should be much
larger afterwards.

Joerg

joerg@britannica.bec.de wrote:

On Thu, Jun 08, 2006 at 04:33:44PM +0100, Mark Cullen wrote:

joerg@britannica.bec.de wrote:

I have a PDC running 1.4.4... If you can get me a coredump from Samba
build with debug symbols, I can try to trace it down. But without that,
it is quite hard.

Joerg

How might I go about building it with debug symbols?

Try adding
CFLAGS= -O2 -g
CXXFLAGS= -O2 -g

to /etc/mk.conf. The smbd binary in the work directory should be much
larger afterwards.

Joerg

Ok that seems to have worked. The built smbd binary is now 6MB as
opposed to the installed 2MB, however, it's not producing a core dump as
far as I can tell.

Mark Cullen wrote:

joerg@britannica.bec.de wrote:

On Thu, Jun 08, 2006 at 04:33:44PM +0100, Mark Cullen wrote:

joerg@britannica.bec.de wrote:

I have a PDC running 1.4.4... If you can get me a coredump from Samba
build with debug symbols, I can try to trace it down. But without that,
it is quite hard.

Joerg

How might I go about building it with debug symbols?

Try adding
CFLAGS= -O2 -g
CXXFLAGS= -O2 -g
to /etc/mk.conf. The smbd binary in the work directory should be much
larger afterwards.

Joerg

Ok that seems to have worked. The built smbd binary is now 6MB as
opposed to the installed 2MB, however, it's not producing a core dump as
far as I can tell.

Ah ha, I had to set `kern.sugid_coredump` and it got put in /tmp. Is
there any particular place you would like it uploaded, or any gdb(?)
commands run etc etc?

Thanks for helping out, again! :)

Is this still present?

I'm not sure, sorry. If I get a bit of free time then I will install DF
1.6(?) on a spare machine again and see what happens.

I believe this used to be an interaction with gcc and varargs. AFAIR it has
been fixed.