Re: Confused...

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



> On Wed, Jul 12, 2006 at 01:03:33PM -0600, Reg Clemens wrote:
> > > > stopped working.  Now it starts running and immediately shows 'Killed'.
> > > > The very first line in the program is a fprintf(stderr, ...) and this message
> > > > does not get printed.
> > > > And for reasons I dont understand, Linux is not dropping a core file.
> > > What does "ulimit -c" tell you?
> > Well, I dont seem to have 'ulimit' and 'limit' complains about the -c argument
> 
> It's a shell built-in -- I think "limit coredumpsize" is the csh equivalent.
> And when you get back "coredumpsize 0 kbytes", which you probably will, as
> it is the default, run "limit coredumpsize unlimited".
> 
> 
> > > Have you tried running it under gdb directly?
> > Yes, but couldnt remember how to give the executing program an argument.
> > Hummm, guess I could just build it in.
> > Ill try that.
> 
> "set args". Or yeah, just hardcode it.
> 

---

OK, dumb, dumb, dumb.
Its been a long time since I looked at this thing, but in fact the file argument
IS hardcoded,- the argument is the name of a FIFO that the program will 
write to later on.

[reg@deneb bin]$ gdb zap3a
GNU gdb Red Hat Linux (6.3.0.0-1.84rh)
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 "i386-redhat-linux-gnu"...Using host libthread_db library "/lib/libthread_db.so.1".

(gdb) run
Starting program: /mnt/i1/Images/bin/zap3a

Program terminated with signal SIGKILL, Killed.
The program no longer exists.
You can't do that without a process to debug.

---

Here is the result of the current limit command

[reg@deneb bin]$ limit
cputime      unlimited
filesize     unlimited
datasize     unlimited
stacksize    unlimited
coredumpsize unlimited
memoryuse    unlimited
vmemoryuse   unlimited
descriptors  1024 
memorylocked 32 kbytes
maxproc      16368 

---

And the top of the program, other than limits things its hard to 
understand what its complaining about before getting to the
first print statement...

---
#include <stdio.h>
#include <sys/types.h>
#include <sys/stat.h>
#include <unistd.h>
#include <string.h>

#define LINES 500000

/* this is the (uncomplteted code to run from AUB to delete
        files (coming in) that are already in the database */

char    lines[LINES][200];
int     Fgets(), qsort();
void    *malloc(), exit();

struct new {
        struct  new *next;
        char    md5cs[34];
} *NEW, *np, *OLD;


int
main()
{
        int     i, n, cmp1();
        char    **Sorted, *f_name, output[250], line[220];
        char    *file_name, *cp, **cpp;
        FILE    *fp, *fp1;
        void    *vp, *bsearch();
        struct stat sbuf;

fprintf(stderr, "aub3a: at top\n");
        f_name = "/home/share/Images/z3";
        if ((fp = fopen(f_name, "r+")) == NULL) {
                fprintf(stderr, "Cant open \"%s\"\n", f_name);
                exit(1);
        }
fprintf(stderr, "aub3a: file open\n");

...

Any more thoughts?
Mabe Im just not seeing something.



-- 
                                        Reg.Clemens
                                        reg@xxxxxxx



[Index of Archives]     [Current Fedora Users]     [Fedora Desktop]     [Fedora SELinux]     [Yosemite News]     [Yosemite Photos]     [KDE Users]     [Fedora Tools]     [Fedora Docs]

  Powered by Linux