similar to: * mod core dump help

Hi, I have a problem with a VFS module that I am developing. The module has been runing fine under 3.0.6, but then I didn't have time to work on it for a while and meanwhile I upgraded samba to the latest sarge debian release 3.0.14a and now that I have got the sources and again recompiled my module and included it into the /usr/lib/samba/vfs dir, its now core dumping. I am sort of at loss

Hello we can enable core dump through /etc/security/limits.conf how can I do it through /proc file system ? Thanks

I''m running Ubuntu Edgy and have 0.22.1 installed from source. I''m running puppetmaster on the box. When I run "puppetd -v -o" on the same machine, I get the error in the file I''ve attached. I was running 0.20.1 just fine from .debs and then updated to 0.22.1 source. Is there any way to cleanly uninstall puppet so I can start over? Any advice as to what is

Hi List, all of a sudden my ssh-add dumps. As always :) I haven't changed anything. In the beginning I thought my encrypted disk key was borked but I re-created a new key and I have the same phenomenon. http://steve.localhost.lu/ssh-add.core http://steve.localhost.lu/ktrace.out steve@laptop-steve ~ $ uname -a FreeBSD laptop-steve.localhost.lu 6.2-RC2 FreeBSD 6.2-RC2 #1: Sun Dec 24 19:31:12

Hey, Im able to reproduce a crash from plockstat everytime Im tracing a JVM pid. I do recall a problem related with this one, but not clear if this has been fixed in U3 or is it planned for U4 ? Any BugID opened for this stack trace: > ::stack libc.so.1`strlen+0x50(100003faa, ffffffff7ffff5c8, ffffffff7eca1114, ffffffff7fffec79, 0, 100003fa9) libc.so.1`snprintf+0x88(ffffffff7ffff8f0, 0,

Hi all, Are there equivalent xe subcommands to ''xm sysrq'' and ''xm dump-core''? I looked up xe''s help message and hidden subcommands in source code but cannot find. -- Regards Yu Zhiguo _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users

Author: rie Repository: /hg/zfs-crypto/gate Revision: 03313218730eac4d34c28c7ddc91858f0fe04c79 Log message: 6340814 ld.so.1 core dump with HWCAP relocatable object + updated statistics Files: update: usr/src/cmd/sgs/include/libld.h update: usr/src/cmd/sgs/libld/common/relocate.c update: usr/src/cmd/sgs/liblddbg/common/liblddbg.msg update: usr/src/cmd/sgs/liblddbg/common/statistics.c update:

In the .xen_pages section of a core dump, is the layout of pages 1:1 with DomU "physical" memory, or are there holes? Thanks James

Dear R Development Team, I compile R-1.9.1 on AIX 5.2 under 2.9-aix51-020209, and xlf 7.1. In order to let R compile successfully under gcc 2.9, I have to change one C statement of file(RHOME//src/modules/X11/devX11.c) line 1768 from "retrun FALSE" to "retrun NULL", following is C code snapshot: newX11Desc * Rf_allocNewX11DeviceDesc(double ps) { newX11Desc *xd;

Author: marks Repository: /hg/zfs-crypto/gate Revision: 30d7e3669aa20772767cb9726d60c32659192c23 Log message: 6395977 unpack dump core when run over NFSv4 over ZFS Files: update: usr/src/cmd/compress/compress.c update: usr/src/cmd/pack/pack.c update: usr/src/cmd/unpack/unpack.c

Hello, I'm testing with asterisk 1.8.3.2 and come across this: Call from one extension to another with: [macro-internal-call] ;ARG1=extension to call exten => s,1,Set(TOCALL=${DB(SIP/${ARG1})}) exten => s,2,Dial(SIP/${TOCALL},60,tT) ... As I had no entry in the asteriskdb, so the SIP uri was empty, and asterisk core dumped with: gdb output: #0 0xb7c7db33 in strchr () from

Hello all, Just a quick note to other Solaris users that upgrading to samba-3.0.5 seems to cause cron to core dump into /var/spool/cron/atjobs. After investigating this for a few days, it appears to be due to the winbind entry in /etc/nsswith.conf. Of course, once I restart the cron daemon, and it picks up the new libnss_winbind and pam_winbind.so files, everything is fine. However, this has left

https://bugzilla.samba.org/show_bug.cgi?id=1448 wayned@samba.org changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |DUPLICATE ------- Additional Comments From wayned@samba.org 2004-06-09 13:54

Here's a simple way to crash brctl (Fedora 8's brctl and tonight's git tree): [root at grok2 brctl]# ./brctl addbr bridge [root at grok2 brctl]# ./brctl show bridge name bridge id STP enabled interfaces . Segmentation fault (core dumped) Take it easy, Ben -- Ben Greear <greearb at candelatech.com> Candela Technologies Inc

Author: nakanon Repository: /hg/zfs-crypto/gate Revision: 256327dbf767068c6616d7e339fe18c6f2e3bd36 Log message: 6336149 *csh* core dump if argv is unset or reset Files: update: usr/src/cmd/csh/sh.c

Hi All. While working on something I noticed core dumps from sshd. They don't seem to be related to what I was working on. It's from the process forked to run the shell. Just after the fork, fatal_remove_all_cleanups() is called, which looks like: fatal_remove_all_cleanups(void) { struct fatal_cleanup *cu, *next_cu; for (cu = fatal_cleanups; cu; cu = next_cu) {

The following patchset is the dump-core take 6. It changes its format into ELF, adds PFN-GMFN/PFN table, HVM support, and IA64 support. Changes from take 5 - changed section name .Xen.xxx -> .xen_xxx - added XENVER_capabilities and XEDNVER_platform_parameters to xen_version elf note for analysis tools to know whether pae or not - added .xen_prstatus section - made format version single

Hi, I'm one of those people who still need to maintain * 1.2 systems and cannot easily upgrade. :-( My 1.2 systems were very stable until I upgraded from 1.2.37 to 1.2.40. I have made some changes within my dialplan but nothing unusual. Today I've had a crash: https://issues.asterisk.org/file_download.php?file_id=25571&type=bug Yesterday I had another:

Author: phitran Repository: /hg/zfs-crypto/gate Revision: 138a94631b14d3dffa268a110113925f2c83be0a Log message: 6345872 rmformat core dump Files: update: usr/src/cmd/rmformat/rmf_misc.c

Package: xen-utils-common Version: 4.1.4-2 Severity: normal Hi, During some research I encountered incorrect information in the man page of xm, about the dump-core functionality: The man page says: "Defaults to dumping the core without pausing the domain if no I<OPTIONS> are specified." When taking a look at the source code of this process, the default behaviour is to actually