install-log-devel — install-log developers' list

[ID] manufacturer of garments and bags in China

[Rachel <ja...@se...>]

Dear Sir,  

I have the pleasure to know your esteemed corp. 

We are a manufacturer & exporter of garments and bags in Quanzhou, China.

I think we can cooperate and supply you with garments as you need.  

The following is some introductions about our company.

       Set up: 1988

       Type: manufacturer & exporter

       Product: knitted garments and bags

       Employees: 1300 persons ( garments factory: 500      bags factory: 800)

       Product data:       

                                  product (main items)                      capacity(/year)

                                  brief                                    2,000,000dzs    

                                  baby body                                1,800,000dzs

                                  boxer short                                200,000dzs

                                  pajama                                      50,000dzs

                                  soft bag                                 1,500,000pcs

                                  hard bag                                   500,000pcs

Mimn order:  300dzs for garments

Payment:  irrevocable L/C at sight

Bank: BANK OF CHINA


Our garment factory mainly specialize in Lady's and men's underwear,

children's wear, baby's wear, pajama, boxer shorts, T-shirt, etc. 

The materials we often use are cotton, T/C, Polyester, Polyamide, 

Elasthan, and Polyamide. Our products are design with PAD system, 

produced with advanced equipment, processed in highly quality control 

system with seasoned workmanship and high efficiency. Our main market 

is Europe, Australia, Japan and America. We also accept the orders designed 

and required by costumers. You can see some pictures of our samples through 

our web http://www.senwer.com. (For more pictures in your interesting, 

pls kindly contact us directly). 
 

Our bag factory was founded in 1988, too. We produce all kinds of bags, 

including rucksacks, travel bags, school bags, PC bags, waist bags, etc. 

And the goods have met a great favor in the Europe countries, Australia 

and America because of their good quality, beautiful design and competitive price.


Thank you very much. Hope you will give us an opportunity to do 

business together and we will try our level best to fulfill your present 

requirement. Should you therefore need any more details for your 

clarification, pls do not hesitate to contact us. And you are welcome 

to visit our factories.


With best regards


Rachel Wang

0086-13960286700

ra...@se...


Jason Chen

MOB:0086-13959893400

jas...@se...


Vicki Wang

0086-13960228599

vi...@se...


-----------------------------------------------------------------------------

SENWER GARMENTS CO., LTD.

ADD: Room F202, Fugui Renjia Building, Liuguan Road, Quanzhou, Fujian, China.

Tel: 0086-595-2506700    Fax: 0086-595-2563400    P.C.:362000

Http://www.senwer.com    E-mail: se...@pu...

-----------------------------------------------------------------------------

[ID] New site

[Andy G. <unu...@op...>]

Work has been moved to http://ioioio.net/devel/install-log/.  You might want 
to check out the cvs tree--it contains several bugfixes and other assorted 
improvements.

-- 
Andy Goth  |  unu...@op...  |  http://ioioio.net/
End communication.

[ID] download

[helen c. <ber...@ms...>]

how to get install.log ?Holen Sie mehr aus dem Web. Unter http://explorer=
.msn.de/intl.asp#de gibt es einen KOSTENLOSEN Download von MSN Explorer.

Re: [ID] Seg. Fault

[Andy G. <unu...@op...>]

On Tue, May 28, 2002 at 11:32:16PM +1000, Glenn McKechnie wrote:
> 	  0x4009d864 in memmove () from /lib/libc.so.6
> 	  (gdb) ba
> 	  #0  0x4009d864 in memmove () from /lib/libc.so.6
> 	  #1  0x4001558c in _dl_debug_mask () from /lib/ld-linux.so.2
> 	  #2  0x6c6d782e in ?? ()

How weird... no idea where the line numbers went.  At the same time,
though, gdb is using the debugging information (it appears earlier in
your script).  I'll look into it later.

> Which means that it's still a mystery as there are no line numbers for
> the relevant segfault?

Hmm.

> Should I stick to version 1.9 or is the /ioioio.net/ version okay?

They're practically identical, as I recall.  One has the beginnings of
new features, but they're not actually used by the main program.

I really need to fix the makefile. ;^)  Compiling and then deleting
files is shameful.

-- 
Andy Goth  |  unu...@op...  |  http://ioioio.net/
User has performed an invalid operation and will be terminated.

Re: [ID] Seg. Fault

[Glenn M. <gra...@op...>]

Andy Goth wrote:
> On Sun, May 26, 2002 at 09:26:59PM +1000, Glenn McKechnie wrote:
> > Andy Goth wrote:
> > Program received signal SIGSEGV, Segmentation fault.
> > 0x40099864 in memmove () from /lib/libc.so.6
> > (gdb) ba
> > #0  0x40099864 in memmove () from /lib/libc.so.6
> > #1  0x4001558c in _dl_debug_mask () from /lib/ld-linux.so.2
> > #2  0x6c6d782e in ?? ()
> > (gdb) q
> 
> Line numbers would be helpful. ;^)  Are you sure you used -g and -ggdb?
> Also, did the ElectricFence banner show up?

Nope, there are no line numbers it would seem

Script started on Tue May 28 22:05:32 2002
 10:05pm $make clean all CFLAGS="-g -ggdb" LIBS="-lefence"
 cc -g -ggdb -MMD -g -c -o package.o package.c
 cc -g -ggdb -MMD -g -c -o editor.o editor.c
 cc -g -ggdb -MMD -g -c -o database.o database.c
 cc -g -ggdb -MMD -g -c -o util.o util.c
 cc -g -ggdb -MMD -g -c -o timestamp.o timestamp.c
 cc -g -ggdb -MMD -g -c -o logger.o logger.c
 cc -g -ggdb -MMD -g -c -o list.o list.c
 cc -g -ggdb -MMD -g -c -o globals.o globals.c
 cc -g -ggdb -MMD -g -c -o config.o config.c
 cc -g -ggdb -MMD -g -c -o install-log.o install-log.c
 rm -f core install-log install-log.o config.o globals.o list.o logger.o
 timestamp.o util.o database.o editor.o package.o install-log.d config.d
 globals.d list.d logger.d timestamp.d util.d database.d editor.d
 package.d
 cc -g -ggdb -MMD -g -c -o install-log.o install-log.c
 cc -g -ggdb -MMD -g -c -o config.o config.c
 cc -g -ggdb -MMD -g -c -o globals.o globals.c
 cc -g -ggdb -MMD -g -c -o list.o list.c
 cc -g -ggdb -MMD -g -c -o logger.o logger.c
 cc -g -ggdb -MMD -g -c -o timestamp.o timestamp.c
 cc -g -ggdb -MMD -g -c -o util.o util.c
 cc -g -ggdb -MMD -g -c -o database.o database.c
 cc -g -ggdb -MMD -g -c -o editor.o editor.c
 cc -g -ggdb -MMD -g -c -o package.o package.c
 cc -g -ggdb -o install-log install-log.o config.o globals.o list.o
 logger.o timestamp.o util.o database.o editor.o package.o -lefence
  10:06pm $gdb ./install-log
  GNU gdb 5.2
  
  Copyright 2002 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 "i686-pc-linux-gnu"...
  (gdb) set args -v 9 1 dump1
  (gdb) r
  Starting program: /mnt/sprb/install-log/install-log -v 9 dump1
  [New Thread 1024 (LWP 24449)]

    Electric Fence 2.2.0 Copyright (C) 1987-1999 Bruce Perens
    <br...@pe...>
    Scanning /bin
    Scanning /lib
    Descending into /lib/modules
    Descending into /lib/modules/2.4.18
    
[...] 
    
    Descending into /mnt/redhat73/sbin
    Descending into /mnt/redhat73/misc
    Scanning for old and deleted files
    Writing database

    Program received signal SIGSEGV, Segmentation fault.
    [Switching to Thread 1024 (LWP 24449)]
    0x4009d864 in memmove () from /lib/libc.so.6
    (gdb) ba
    #0  0x4009d864 in memmove () from /lib/libc.so.6
    #1  0x4001558c in _dl_debug_mask () from /lib/ld-linux.so.2
    #2  0x6c6d782e in ?? ()
    (gdb) q
    The program is running.  Exit anyway? (y or n) y
     10:08pm $exit
     Script done on Tue May 28 22:08:24 2002

    

That was using the source from your site at /ioioio.net/  it had a 2002
date in the tree so I went for it :-). This next script log is for
install-log-1.9, with a couple of experimental breakpoints in it. I'm
just getting the feel of it and seeing if line numbers would come up.


Script started on Tue May 28 22:24:53 2002
 10:24pm $make clean all CFLAGS="-g -ggdb" LIBS="-lefence"
 Makefile:29: install-log.d: No such file or directory
 Makefile:29: config.d: No such file or directory
 Makefile:29: globals.d: No such file or directory
 Makefile:29: list.d: No such file or directory
 Makefile:29: logger.d: No such file or directory
 Makefile:29: timestamp.d: No such file or directory
 Makefile:29: util.d: No such file or directory
 Makefile:29: database.d: No such file or directory
 Makefile:29: editor.d: No such file or directory
 ./depend.sh -g -ggdb editor.c > editor.d
 ./depend.sh -g -ggdb database.c > database.d
 ./depend.sh -g -ggdb util.c > util.d
 ./depend.sh -g -ggdb timestamp.c > timestamp.d
 ./depend.sh -g -ggdb logger.c > logger.d
 ./depend.sh -g -ggdb list.c > list.d
 ./depend.sh -g -ggdb globals.c > globals.d
 ./depend.sh -g -ggdb config.c > config.d
 ./depend.sh -g -ggdb install-log.c > install-log.d
 rm -f core install-log install-log.o config.o globals.o list.o logger.o
 timestamp.o util.o database.o editor.o install-log.d config.d globals.d
 list.d logger.d timestamp.d util.d database.d editor.d
 cc -g -ggdb -c -o install-log.o install-log.c
 cc -g -ggdb -c -o config.o config.c
 cc -g -ggdb -c -o globals.o globals.c
 cc -g -ggdb -c -o list.o list.c
 cc -g -ggdb -c -o logger.o logger.c
 cc -g -ggdb -c -o timestamp.o timestamp.c
 cc -g -ggdb -c -o util.o util.c
 cc -g -ggdb -c -o database.o database.c
 cc -g -ggdb -c -o editor.o editor.c
 cc -g -ggdb -o install-log install-log.o config.o globals.o list.o
 logger.o timestamp.o util.o database.o editor.o -lefence
  10:25pm $gdb ./install-log
  GNU gdb 5.2
  Copyright 2002 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 "i686-pc-linux-gnu"...
  (gdb) set args -v 9 dump1-19
  (gdb) r
  Starting program: /mnt/spra/blfs/install-log-1.9/install-log -v 9
  dump1-19
  [New Thread 1024 (LWP 25387)]

    Electric Fence 2.2.0 Copyright (C) 1987-1999 Bruce Perens
    <br...@pe...>
    Scanning /bin
    Scanning /lib
    Descending into /lib/modules
    Descending into /lib/modules/2.4.18
    
[...] 
    
    Descending into /mnt/redhat73/sbin
    Descending into /mnt/redhat73/misc
    Scanning for old and deleted files
    Writing database
    [Switching to Thread 1024 (LWP 25428)]

    Breakpoint 1, replace (context=0xbffff6f8, context_cap=0xbffff700,
    from=0x804b2bb "%", to=0x804b2bd "%%") at util.c:44
    44		int from_len = strlen(from);
    (gdb) b database.c:14
    Breakpoint 2 at 0x804a796: file database.c, line 14.
    (gdb) c
    Continuing.

    Breakpoint 1, replace (context=0xbffff6f8, context_cap=0xbffff700,
    from=0x804b2bb "%", to=0x804b2bd "%%") at util.c:44
    44		int from_len = strlen(from);
    (gdb) disable 1
    (gdb) r
    The program being debugged has been started already.
    Start it from the beginning? (y or n) y
    Starting program: /mnt/spra/blfs/install-log-1.9/install-log -v 9
    dump1-19-util-42
    [New Thread 1024 (LWP 25431)]

      Electric Fence 2.2.0 Copyright (C) 1987-1999 Bruce Perens
      <br...@pe...>
      [Switching to Thread 1024 (LWP 25431)]

      Breakpoint 2, read_db () at database.c:16
      16		List* node = &prev_files;
      (gdb) r
      The program being debugged has been started already.
      Start it from the beginning? (y or n) y
      Starting program: /mnt/spra/blfs/install-log-1.9/install-log -v 9
      dump1-19-util-42
      [New Thread 1024 (LWP 25432)]

        Electric Fence 2.2.0 Copyright (C) 1987-1999 Bruce Perens
	<br...@pe...>
	[Switching to Thread 1024 (LWP 25432)]

	Breakpoint 2, read_db () at database.c:16
	16		List* node = &prev_files;
	(gdb) c
	Continuing.
	/mnt/spra/blfs/install-log-1.9/install-log: "dump1-19-util-42"
	has already been logged; use --force to update it

	Program exited with code 01.
	(gdb) set args dump1-19-util-4 database.c14
	(gdb) r
	Starting program: /mnt/spra/blfs/install-log-1.9/install-log
	dump1-19-util-database.c14
	[New Thread 1024 (LWP 25433)]

	  Electric Fence 2.2.0 Copyright (C) 1987-1999 Bruce Perens
	  <br...@pe...>
	  [Switching to Thread 1024 (LWP 25433)]

	  Breakpoint 2, read_db () at database.c:16
	  16		List* node = &prev_files;
	  (gdb) disable 2
	  (gdb) c
	  Continuing.

	  Program received signal SIGSEGV, Segmentation fault.
	  0x4009d864 in memmove () from /lib/libc.so.6
	  (gdb) ba
	  #0  0x4009d864 in memmove () from /lib/libc.so.6
	  #1  0x4001558c in _dl_debug_mask () from /lib/ld-linux.so.2
	  #2  0x6c6d782e in ?? ()
	  (gdb) bt
	  #0  0x4009d864 in memmove () from /lib/libc.so.6
	  #1  0x4001558c in _dl_debug_mask () from /lib/ld-linux.so.2
	  #2  0x6c6d782e in ?? ()
	  (gdb) q
	  The program is running.  Exit anyway? (y or n) y
	   10:58pm $exit
	   Script done on Tue May 28 22:58:55 2002


Which means that it's still a mystery as there are no line numbers for
the relevant segfault?

> 
> > At one stage gdb complained about lack of memory, a google search of the
> > error string (my references are lost - don't ask) confirmed that to be the 
> > case. I'm surprised as I have 3x256meg available; perhaps I should set
> > aside some disk space after all.
> 
> Was it gdb that was having the problem or install-log?  I don't recall
> throwing any specific out-of-memory errors...

gdb, but its behaved itself since.


I found a few tutorials for gdb so I'll attempt to improve my understanding
and see what damage I can do then.

Should I stick to version 1.9 or is the /ioioio.net/ version okay?

-- 
Cheers
 Glenn


"It is better to have tried and failed than to have failed to try, but
the result's the same."
- Mike Dennison

Re: [ID] Seg. Fault

[Andy G. <unu...@op...>]

On Sun, May 26, 2002 at 09:26:59PM +1000, Glenn McKechnie wrote:
> Andy Goth wrote:
> Program received signal SIGSEGV, Segmentation fault.
> 0x40099864 in memmove () from /lib/libc.so.6
> (gdb) ba
> #0  0x40099864 in memmove () from /lib/libc.so.6
> #1  0x4001558c in _dl_debug_mask () from /lib/ld-linux.so.2
> #2  0x6c6d782e in ?? ()
> (gdb) q

Line numbers would be helpful. ;^)  Are you sure you used -g and -ggdb?
Also, did the ElectricFence banner show up?

> At one stage gdb complained about lack of memory, a google search of the
> error string (my references are lost - don't ask) confirmed that to be the 
> case. I'm surprised as I have 3x256meg available; perhaps I should set
> aside some disk space after all.

Was it gdb that was having the problem or install-log?  I don't recall
throwing any specific out-of-memory errors...

> > send it to me.  I can cat it to an xargs touch in a pseudo-chroot and
> > then run the latest install-log on the results.
> 
> I was with you until "I can cat it to an" Looks like I have some more man paging
> to do.

cat list | xargs touch

This will make an empty file for each line in "list".  It will also barf
on subdirectories, heh, so don't bother trying it.

-- 
Andy Goth  |  unu...@op...  |  http://ioioio.net/
User has performed an invalid operation and will be terminated.

Re: [ID] Seg. Fault

[Glenn M. <gra...@op...>]

Andy Goth wrote:

I broke it, which is to say that it now works.
This is extremely unfortunate as I'm also having trouble getting it to
segfault again, but break it I will!


[...] 
> Do this.
> 
> script crash.log
> make clean all CFLAGS="-g -ggdb" LIBS="-lefence"
> gdb install-log
> set args __fill_in_the_blank__
> r
> <crash!>
> ba
> q
> exit
> 
> Send me the log (doctored as you see fit).
> 
> Oh, and -lefence comes from Bruce Perens's indispensible ElectricFence.
> 

I found ElectricFence-2.1 from ftp://ftp.perens.com/pub/ElectricFence/
unfortunately it barfed with an error.

page.c:34: conflicting types for `sys_errlist'
/usr/include/stdio.h:552: previous declaration of `sys_errlist'

I initially commented out the "problem" in stdio.h. I then came to my
senses and fetched ElectricFence-2.2.2 from the beta section. and am now
using that one :-)

I did one run with my "patched" version of efence but then realized that 
gdb install-log should probably have been gdb ./install-log

that result was....

Program received signal SIGSEGV, Segmentation fault.
0x40099864 in memmove () from /lib/libc.so.6
(gdb) ba
#0  0x40099864 in memmove () from /lib/libc.so.6
#1  0x4001558c in _dl_debug_mask () from /lib/ld-linux.so.2
#2  0x6c6d782e in ?? ()
(gdb) q


When I manage to break install-log again I'll let you know. I should
know I little more of what I'm doing by then too ;-)

At one stage gdb complained about lack of memory, a google search of the
error string (my references are lost - don't ask) confirmed that to be the 
case. I'm surprised as I have 3x256meg available; perhaps I should set
aside some disk space after all.

As I said I'm pedalling hard. :-)


> send it to me.  I can cat it to an xargs touch in a pseudo-chroot and
> then run the latest install-log on the results.

I was with you until "I can cat it to an" Looks like I have some more man paging
to do.

Thanks for the time ( and the debugging example ). I'll send some more pieces later.

-- 
Cheers
 Glenn

Conscious is when you are aware of something and conscience is when you
wish you weren't.

Re: [ID] Seg. Fault

[Andy G. <unu...@op...>]

On Fri, May 24, 2002 at 12:30:34AM +1000, Glenn wrote:
> I have a suspicion that it relates to the database size as the problem
> first presented itself after building Xfree. A few deletes and rebuilds
> of various packages hinted that it was only large packages affecting it.

I'm not sure I ever tested it against XFree86, but I think I had it scan
my entire system a few times.  I can't remember for sure--it's been a
long, long time since I modified the code.

> the core dump....
>  00:03am $gdb ./install-log core     
>  GNU gdb 5.2
>  Copyright 2002 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 "i686-pc-linux-gnu"...
>  Core was generated by `./install-log -v 9 coredump5'.
>  Program terminated with signal 11, Segmentation fault.
>  Reading symbols from /lib/libc.so.6...done.
>  Loaded symbols for /lib/libc.so.6
>  Reading symbols from /lib/ld-linux.so.2...done.
>  Loaded symbols for /lib/ld-linux.so.2
>  #0  0x400960b9 in chunk_realloc () from /lib/libc.so.6
>  (gdb) where
>  #0  0x400960b9 in chunk_realloc () from /lib/libc.so.6
>  #1  0x401502bc in __DTOR_END__ () from /lib/libc.so.6
>  Cannot access memory at address 0x10
>  (gdb) quit

A crash in realloc indicates that I overflowed a buffer somewhere, freed
something twice, or otherwise scribbled all over malloc's internal
tables.

> and the output of the program itself...
>  install-log -v9 coredump4
>  
>  much snipping
> [...]
> 
>  Adding /etc/cups/printers.conf
>  Adding /etc/cups/mime.convs
>  Adding /etc/cups/mime.types
>  Adding /etc/cups/ppds.dat
>  Adding /etc/cups/pstoraster.convs
>  Adding /etc/cups/command.types
>  Adding /etc/cups/printers.conf.O
>  Adding /etc/printcap
>  Descending into /etc/foomatic
>  Adding /etc/foomatic/filter.conf
>  Adding /etc/xinetd.conf
>  Scanning for old and deleted files
>  Writing database
>  Segmentation fault (core dumped)
> 
> 
> I get the start of an output file under /var/install-logs which is
> consist in size....
> 
> ls -al 
> 
> -rw-r--r--    1 root     root        12288 May 23 21:46 coredump
> -rw-r--r--    1 root     root        12288 May 23 23:06 coredump2
> -rw-r--r--    1 root     root        12288 May 23 23:29 coredump3
> -rw-r--r--    1 root     root        12288 May 23 23:34 coredump4
> -rw-r--r--    1 root     root        12288 May 24 00:03 coredump5
> 
> from memory this size similarity existed in the other logging attempts,
> however the size was different ie:- not 12288 bytes ( The other attempts
> were a while ago )

Hmm.  I did a lot of weirdness with memory management in an attempt to
avoid unnecessary malloc and realloc calls.  I probably screwed up in
several places.  On the other hand, I reused a lot of my code in other
projects, and it worked.  On the other, other hand, I do recall finding
bugs but never patching the install-log tree.  Hmm.  Hmm.

> compile arguments, example....
> cc -O2 -march=i686 -mcpu=i686 -pipe  -I. -MMD -g -c -o editor.o editor.c
> 
> This is on a LFS 3.3 base system.

Wow, LFS sure has marched on a long way since my last build! ;^)  Guess
it's time to update.

> I can supply more details if required, and hopefully assist with some
> debugging if the process involved is reasonably simple. If it's not
> simple; I'll pedal really hard!

Do this.

script crash.log
make clean all CFLAGS="-g -ggdb" LIBS="-lefence"
gdb install-log
set args __fill_in_the_blank__
r
<crash!>
ba
q
exit

Send me the log (doctored as you see fit).

Oh, and -lefence comes from Bruce Perens's indispensible ElectricFence.

> This is a neat, fast program. I was using a bash script, modified from
> Gerard Beekmans lfs-install script but it was painfully slow on a large
> system. Your effort certainly speeds up that process, except for this
> nagging problem :-(

Heh, install-log comes from a very, very short script (more like a
snippet) from Gerard, nothing more than a call to find.  Versions prior
to 1.9 were written in bash; you might want to check them out.  In fact,
try generating a database with one of them that would crash 1.9; then
send it to me.  I can cat it to an xargs touch in a pseudo-chroot and
then run the latest install-log on the results.

-- 
Andy Goth  |  unu...@op...  |  http://ioioio.net/
User has performed an invalid operation and will be terminated.

[ID] Seg. Fault

[Glenn <gra...@op...>]

I started using install-log 1.9 and it worked well, however it now insists 
on segfaulting.

I have a suspicion that it relates to the database size as the problem
first presented itself after building Xfree. A few deletes and rebuilds
of various packages hinted that it was only large packages affecting it.

the core dump....
 00:03am $gdb ./install-log core     
 GNU gdb 5.2
 Copyright 2002 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 "i686-pc-linux-gnu"...
 Core was generated by `./install-log -v 9 coredump5'.
 Program terminated with signal 11, Segmentation fault.
 Reading symbols from /lib/libc.so.6...done.
 Loaded symbols for /lib/libc.so.6
 Reading symbols from /lib/ld-linux.so.2...done.
 Loaded symbols for /lib/ld-linux.so.2
 #0  0x400960b9 in chunk_realloc () from /lib/libc.so.6
 (gdb) where
 #0  0x400960b9 in chunk_realloc () from /lib/libc.so.6
 #1  0x401502bc in __DTOR_END__ () from /lib/libc.so.6
 Cannot access memory at address 0x10
 (gdb) quit



and the output of the program itself...
 install-log -v9 coredump4
 
 much snipping
[...]

 Adding /etc/cups/printers.conf
 Adding /etc/cups/mime.convs
 Adding /etc/cups/mime.types
 Adding /etc/cups/ppds.dat
 Adding /etc/cups/pstoraster.convs
 Adding /etc/cups/command.types
 Adding /etc/cups/printers.conf.O
 Adding /etc/printcap
 Descending into /etc/foomatic
 Adding /etc/foomatic/filter.conf
 Adding /etc/xinetd.conf
 Scanning for old and deleted files
 Writing database
 Segmentation fault (core dumped)


I get the start of an output file under /var/install-logs which is
consist in size....

ls -al 

-rw-r--r--    1 root     root        12288 May 23 21:46 coredump
-rw-r--r--    1 root     root        12288 May 23 23:06 coredump2
-rw-r--r--    1 root     root        12288 May 23 23:29 coredump3
-rw-r--r--    1 root     root        12288 May 23 23:34 coredump4
-rw-r--r--    1 root     root        12288 May 24 00:03 coredump5

from memory this size similarity existed in the other logging attempts,
however the size was different ie:- not 12288 bytes ( The other attempts
were a while ago )


compile arguments, example....
cc -O2 -march=i686 -mcpu=i686 -pipe  -I. -MMD -g -c -o editor.o editor.c

This is on a LFS 3.3 base system.

I can supply more details if required, and hopefully assist with some
debugging if the process involved is reasonably simple. If it's not
simple; I'll pedal really hard!


This is a neat, fast program. I was using a bash script, modified from
Gerard Beekmans lfs-install script but it was painfully slow on a large
system. Your effort certainly speeds up that process, except for this
nagging problem :-(


-- 
Cheers
 Glenn

The person who's taking you to lunch has no intention of paying.

[ID] Enhancement suggestion?

[Mark C. <ma...@ex...>]

Hi,

Ive just started using install-log for my lfs system and so far its
proved great!!

But may I suggest an enhancement on the actuall logging it does.

I don't know if this is possable, but when you enter:

install-log gpm-1.19.3

then it gives you an option to include a desciption of the package, like
in slackware:

PACKAGE NAME:     gpm
COMPRESSED PACKAGE SIZE:     210 K
UNCOMPRESSED PACKAGE SIZE:     550 K
PACKAGE MD5SUM: 0388881351933e27c7af7eb1d494c2d4
PACKAGE DESCRIPTION:
gpm:      gpm-1.19.3
gpm:
gpm: The general purpose mouse server, or gpm, allows you to use mouse
gpm: to cut and paste text from the screen.  It also acts as a mouse
gpm: server for applications running on the Linux console, such as the
gpm: Midnight Commander file manager and dialog.
gpm: 
FILE LIST:
./
usr/
usr/bin/
usr/bin/mev
usr/bin/gpm
usr/doc/gpm-1.19.3/
usr/doc/gpm-1.19.3/Announce
usr/doc/gpm-1.19.3/COPYING
usr/doc/gpm-1.19.3/ChangeLog
usr/doc/gpm-1.19.3/FAQ
usr/doc/gpm-1.19.3/README
usr/doc/gpm-1.19.3/README.microtouch
usr/doc/gpm-1.19.3/README.synaptics
usr/doc/gpm-1.19.3/README.twiddler


Sorry if this is out of place, but *IMHO* this would add another usefull
utility to install-log.
this could be an option: install-log -d <description-file> <program>

So it can be turned of is needed to.

As I can only program in Perl, I cannot offer much help in C, but it
should be fairly easy, if I can work out how, I will send a patch in is
this could be added in 2.0

Mark


-- 

[ID] Re: idea of evolution for install-log

[Andy G. <unu...@op...>]

On Sunday, February 17, 2002 4:18, you wrote:
> Hi,
>
> One problem with install-log :
> When a file belongs to 2 packages, deleting one package
> may prevent the other package from working.

I've seen that before.  Workaround:

grep -F "$(cat /var/install-logs/* | sort | uniq -d)" /var/install-logs/*

It's slow, and it requires a lot of user intervention, but it works.  Right 
now it tells me that XFree86 and zlib both provide the same man page.  I 
should fix that. ;^)

> Idea :
> You should create a file that contains all the files of all
> the packages and the number of packages that uses this file.
>
> Example :
> Package A installs /usr/bin/file1, /usr/bin/file2 and /usr/bin/file3
>
> Install-log would produce the file packageA with :
> /usr/bin/file1
> /usr/bin/file2
> /usr/bin/file3
>
> Install-log would update the file allfiles :
> /usr/bin/file1 1
> /usr/bin/file2 1
> /usr/bin/file3 1
>
> Then, package B installs /usr/bin/file3, /usr/bin/file4 and /usr/bin/file5
>
> Install-log would produce the file packageB with :
> /usr/bin/file3
> /usr/bin/file4
> /usr/bin/file5
>
> Install-log would update the file allfiles :
> /usr/bin/file1 1
> /usr/bin/file2 1
> /usr/bin/file3 2
> /usr/bin/file4 1
> /usr/bin/file5 1
>
> Then, delete of packageA ( with a script ) would delete the file :
> /usr/bin/file1
> /usr/bin/file2
> => /usr/bin/file3 is not deleted because it is used by packageB
>
> And would update the file allfiles :
> /usr/bin/file3 1
> /usr/bin/file4 1
> /usr/bin/file5 1
>
> Hope it will inspire u :)

Hey, thanks!  That'll definitely help.  I was wondering how to solve that 
problem without reading the entire database every time.  Of course, it would 
also be possible to beef up this file by listing the names of the packages 
instead of (or in addition to) the numbers so that the user at a glance can 
identify what packages a file belongs to.  (Right now I just use grep.)

-- 
Andy Goth  |  unu...@op...  |  http://www.pengaru.com/~andy/
User has performed an invalid operation and will be terminated.

[ID] Meilleurs Vœux pour 2002 : année de mémoire, de mobilisation, d'action, de justice et de sérénité - Appel au soutien moral et financier

[Habib HAIBI<ha...@fr...>]

Meilleurs Vœux pour 2002 : année de mémoire, de mobilisation, 
d'action, de justice et de sérénité - Appel au soutien moral et 
financier

========================
M. Habib HAIBI,
7, Aguesseau St.
69007 LYON - France
Tél. 00 33 4 72 73 19 08 - Fax 00 33 4 78 61 39 27 
Email : ha...@fr...
http://haibi.free.fr


Je suis qualifié pour exprimer mes voeux pour le Nouvel An à 
tous les survivants et les familles des victimes des attaques 
terroristes, au peuple américain, ses dirigeants, ses institutions, 
son président et tous les combattants de la liberté, loin de leurs 
foyers, tout autour du monde! 

Je suis fier de vous dire avec gratitude combien Les USA sont 
puissants, démocratiques et qualifiés pour défendre la liberté et la 
démocratie avec humanisme et sérénité.

L'ennemi du progrès du genre humain peut encore frapper. La 
liberté et la démocratie peuvent être encore sous attaques!

Personne ne s'imaginait que cela pouvait arriver et c'est arrivé en 
ce jour pacifique du 11 septembre 2001

Personne ne s'imaginait que cela pouvait arriver… en France et 
c'est arrivé le 26 février 2001 quand les magistrats du parquet de 
Lyon, par impulsion suicidaire et préméditée, ont eu recours à 
l'arbitraire pour entraver l'action Publique mise en Mouvement : ils 
ont requis l'expertise psychiatrique de la Partie Civile par l'action 
avant de l'entendre dans ses accusations !

Cette dérive obscurantiste a dépassé tout entendement

C'est arrivé un jour pacifique pour moi et pour les institutions de la 
République en France.

Le réquisitoire aux fins de l'expertise psychiatrique de la partie 
civile par l'action, avant de l'entendre dans ses accusations, 
constitue une atteinte obscurantiste à l'intégrité de la personne 
de la partie civile et surtout un attentat aux valeurs 
fondamentales de la société civilisée et une infamie assénée à la 
République et ses Institutions:
- à tous les martyrs de la liberté qui ont payé de leur vie la 
défense des personnes et des biens et des valeurs 
fondamentales et universelles de la République.

- à tous ceux qui dans l'exercice de leurs fonctions, au nom du 
devoir de servir, exposeraient leurs vies, sans hésitation, pour la 
défense de ces mêmes valeurs

- à tous les hommes ou femmes de bonne volonté, citoyens 
anonymes, élevés sur la foi en une société pacifiée par 
l'avènement de la République, la crainte des lois et l'indéfectibilité 
de l'Etat, de la Justice et des Institutions en Démocratie.

J'étais, longtemps avant le WTC l'autre "point zéro" de la planète 
qui a subit les premières vagues d'attaque contre les institutions 
de la République, la liberté et les droits de l'homme … en France !

Il y a eu trois autres attaques avec la même détermination, 
diabolique et suicidaire, de stopper l'action publique 
régulièrement mise en mouvement !

J'ai fait face à l'adversité en mettant en accusation 15 magistrats, 
saisis par la foudre de l'action publique en colère, 
nominativement impliqués, des deux juridictions de Lyon tout rôle 
et rang confondus pour abus d'autorité aggravé et trafic 
d'influence aggravé. 

Une fois que vous avez pris la mesure de l'attaque contre les 
valeurs universelles de la liberté et la justice en démocratie en 
France… et assimilé la grandeur de la querelle qui m'anime … 
Votre réaction sera vivement souhaitée et sollicitée !

Je recevrai vos contributions morales et financières comme une 
juste consolation pour le grand préjudice moral que je subis dans 
l'attente de la réparation de la faute lourde par la justice et l'Etat.

Souvenez-vous que la paix civile fut conquise au prix de feu, de 
sang et de sacrifices… avec pour objectif le règne absolu et 
égalitaire de la loi.

Imaginez les victimes du 11 septembre 2001 dans un monde 
sans liberté, sans justice et sans démocratie…

Imaginez tous les sacrifices de tous les combattants de la liberté, 
depuis deux siècles et plus, laissés pour compte et discrédités en 
une seule journée d'attaques perpétrées par les forces 
diaboliques de l'arbitraire et de l'obscurantisme dans le pays qui a 
donné naissance au reigne de la loi, l'avènement de la 
République et les droits de l'homme.

Une nouvelle ère a commencé où le grand pays que sont les 
Etats Unis vont guider et pour longtemps l'impulsion de l'alerte et 
de la réaction pour perpétuer la liberté et la justice en 
démocraties. C'est aussi votre combat et le combat de tous les 
hommes libres.

Merci au président des Etats Unis pour son leadership, l'immense 
puissance de son pays et sa sérénité.
Merci à tous d'avoir lu et compris ce message. 
Merci pour vos réactions et vos contributions.
==========================
Ces contributions sont souhaitées à la hauteur de 500 $ ou euros 
et plus pour tous les représentants élus des peuples, sénateurs et 
députés, quelque soit leur pays et quelque soit le moyen utilisé 
pour les alerter des attaques contre la démocratie et de la colère 
de l'action Publique en mouvement : "ma tristesse s'est muée en 
colère et la colère en résolution "!
(ma conviction est que si de tels actes ont pu se produire c'est à 
cause d'un climat de permissivité qui a pu s'installer par l'absence 
du contrôle de l'exécutif par le pouvoir législatif…).
=======
vous pouvez verser directement vos contributions financières sur 
le compte : 
RIP  RELEVE D'IDENTITE BANCAIRE
20041   01007   1112632 F038  69   
IBAN IDENTIFIANT INTERNATIONAL
FR  53  20041  01007  1112632 F 038  69
Ou envoyer un mandat cash à mon nom et à mon adresse.
================================ 
Les contributions seront libres et bienvenues de la part de tout 
autre citoyen sensible à l'idée de vivre dans une société pacifiée 
par la crainte des lois et la crédibilité des institutions 
démocratiques.
============

Mon objectif est de réunir 10 000 réactions à 100 $ ou euros 
chacune : vous pouvez m'aider à atteindre ce but.
Je serai, à coup sûr, un homme riche! 
Mais je ne recouvrerai la paix intérieure avant que justice soit 
faite! 
'J'ai un rêve"! La justice sera faite !

============
Le site où est publié l'ensemble du dossier est en français, vous 
pouvez vous aider pour la traduction par un moteur de traduction 
sur internet.
http://haibi.free.fr
============
Cette mailing liste, non exhaustive, est composée de 30 000 
emails :
des représentants élus, les représentants de l'Etat,  hauts 
fonctionnaires, magistrats, avocats, journalistes, chefs 
d'entreprise, président ou membre d'association, profession 
libérale ou tout autre simple citoyen intéressé par la vie sociale, 
administrative et judiciaire.
=======================
Vous pourrez discuter en circuit interne non publié sur le net en 
vous abonnant au groupe créé pour cet objet "Il n'y a pas 
d'alternative à la justice en république en france"
Coordonnées du groupe :
Email du groupe : lec...@sm... 
Email du gestionnaire : 
lec...@sm... 
Pour devenir membre : 
lec...@sm... 
Pour ne plus être membre : 
lec...@sm... 
Accueil du groupe : 
http://smartgroups.wanadoo.fr/groups/lecitoyen.laloi.larepubliqu
e 
======================
Si vous ne vous sentez pas concerné, vous pouvez demander à 
ce que votre email soit effacer en exprimant votre volonté à 
l'adresse email : ha...@fr...

Merci encore de participer à l'alerte et au suivi de l'action 
publique en mouvement, et au soutien moral et financier de la 
partie civile par l'action.
===================================
===================================
===================================
===================================
===================================
===================================
===================================
===================================
===================================
===================================
===================================
===================================
===================================
===================================================
===================
===================================
===================================
===================================
===================================
===================================
===================================
===================================
===================================
===================================
===================================
===================================
===================================
===================================
===================================
===================================
===================================
===================================
===================================
===================================
===================================
===================================
===================================
===================================
===================================
===================================
===================================
===================================
===================================
===================================
===================================
===================================
===================================
===================================
===================================
===================================
===================================
===================================
===================================
===================================
===================================
===================================
===================================
===================================
===================================
===================================
===================================
===================================
===================================
===================================
===================================
===================================
===================================
===================================
===================================
===================================
===================================
===================================
===================================
===================================
===================================
===================================
===================================
===================================
===================================
ceci n'est pas un spam
vous pourrez en recevoir une version en anglais
Merci !
NEVER SEND SPAM. IT IS BAD.

[ID] Fwd: Re: checkinstall

[Andy G. <unu...@op...>]

----------  Forwarded Message  ----------

Subject: Re: checkinstall
Date: Sun, 23 Dec 2001 11:28:05 -0600 (CST)
From: Felipe Sanchez <iz...@as...>
To: Andy Goth <unu...@op...>

I don't remember any mention of install-log but then again, I lost nearly
all my mail archives (including some unread mail) in a serious server
crash a months ago..  :)


After a quick review of install-log, it's documentation and it's code
(specially logger.c) I found it a lot more like installwatch
(http://asic-linux.com.mx/~izto/installwatch.html#installwatch) than
checkinstall. Installwatch is a file system changes logger, wich creates
log files containing all the changes, just like install-log. What it
(installwatch) doesn't do is the database administration. Which -in my
opinion- should be best left to the standard package administration
utilities.

Since install-log was written with the LFS project in mind the fact that
it does it's own package database administration is understandable.

Checkinstall on the other hand aims to be an easy and efficient way to
build standard packages (slackware .tgz, debian .deb or may others' .rpm)
from a source tarball installation (Or any other, you could even make a
package out of a "rpm -i package.rpm"). There are other plans for it in
the future, you should read the TODO file in checkinstall's distribution.


I mentioned earlier the logger.c file in install-log. I looks like a
"find" implementation (which maybe you used in the previous bash-script
versions) to find what has changed in the installation. Maybe you should
try installwatch to do that job. It's way faster and often just as
accurate as a "find / -atime bla bla". A find-based approach will often
include files that you didn't intend to include but will get caught
because they changed at the same time you used the "find". A installwatch
(LD_PRELOAD) base approach will get exactly the ones changed by the
concerned process, except in the cases were it is a SUID process. A better
way would be to use ptrace(), which is what I'm working on right now  :)

OK, thank you for your message and good luck. Maybe you'd be interested in
joining the checkinstall mailing list: che...@as...

Send an empty message to che...@as... to
subscribe.



Felipe Sanchez.

-------------------------------------------------------

-- 
Andy Goth  |  unu...@op...  |  http://www.pengaru.com/~andy/
User has performed an invalid operation and will be terminated.

[ID] Fwd: Re: cannot install install-log: no rule to make target "install". Stop.

[Andy G. <unu...@op...>]

Heh, something I *still* need to fix...

----------  Forwarded Message  ----------

Subject: Re: cannot install install-log: no rule to make target "install". 
Stop.
Date: Mon, 31 Dec 2001 01:58:36 -0600
From: Andy Goth <unu...@op...>
To: Miranda or Gullit-Franklen <shu...@ne...>

On Monday, December 24, 2001 1:41, you wrote:
> Hi,
>
> I find that install-log is a great news to users who compile and build
> programs from source. I have downloaded and decompressed install-log.
> Every time I type make install (or make and then make install) the
> message :" make : no rule to make target 'install'. Stop. " appears. (No
> other error messages seem to appear) And the program is not installed then.

It's my own mistake.  I really should fix it and release a 1.9b, but I don't
feel like it. ;^)

> Could you please tell me what's going wrong? Or point to any clue that I
> can check for errors? My distribution is Linux Mandrake 8.0.

To install, do the following:

su
<enter password>
cp install-log /usr/bin
cp install-log.rc /etc
mkdir /var/install-logs
touch /var/install-logs/.timestamp
exit

It was so easy I forgot to do it.  Heh.

You might want to read my install-log hint (at least section 1):

http://hints.linuxfromscratch.org/hints/install-log.txt

I just wrote it recently.

> Thank you very much for your attention. Also thanks for developing
> programs for us.

No problem.

--
Andy Goth  |  unu...@op...  |  http://www.pengaru.com/~andy/
User has performed an invalid operation and will be terminated.

-------------------------------------------------------

-- 
Andy Goth  |  unu...@op...  |  http://www.pengaru.com/~andy/
User has performed an invalid operation and will be terminated.

[ID] Re: install-log

[Andy G. <unu...@op...>]

On Sunday, October 7, 2001 10:14, you wrote:
> Hi,
>
> I've just been trying out your install-log program. Seems very cool.  But
> when I try to install version 1.9 by giving the make install command I get
> a No rule to make target 'install' error.

Holy crud, you're right!  I remember adding an 'install' target sometime in 
the past, but it must have been lost.

Okay, here's your fix.

--- Makefile.old        Wed Oct 10 01:44:51 2001
+++ Makefile    Wed Oct 10 01:44:27 2001
@@ -27,6 +27,10 @@
 clean:
        -rm -f core $(PROGRAM) $(OBJ) $(DEP)

+# Place install-log in system directories
+install: all
+       install -m 755 $(PROGRAM) /usr/bin
+       install -m 644 install-log.rc /etc
+
 # Tell make about special (non-file) targets
-.DEFAULT: all
 .PHONY: all clean run install

Interesting how we never caught that...

(I'll place this change in the cvs repository.)

Cameron, please don't try using the latest cvs version.  It's just for us to 
play around with and won't do anything useful unless you use a release 
version of main.

Grr!  cvs problems... up-to-date check failed??

> Then I tried version 1.4 which worked perfectly on my Redhat system. As I
> said, very cool. But when I run it on my new LFS partition it does not seem
> to pick up any additions to the /usr/bin directory.

Please go "back" to 1.9 and see if this problem persists.  Note that in 1.9 
we expanded the configuration possibilities a tad.  Oh, and we changed 
install-log from a shell script to a C program. ;^)  "Might as well," we said.

> Changes elsewhere are
> detected. I can't seem to track down the reason for this. I have not
> altered the script in any way. The permissions on /usr/bin are the same as
> those on /bin and changes to the latter are detected. I get the same
> problem both when I boot up into the LFS partition and when I chroot to it.
>
> Any idea what is causing this problem?

Lots of things, probably.  I just noticed that inside the 1.4 release the 
version number is still 1.3!  Anyway, try 1.9 with the patched Makefile and 
tell us how you fare.

-- 
Andy Goth  |  unu...@op...  |  http://null.cc.uic.edu/~andy/

Re: [ID] Hey

[Andy G. <unu...@op...>]

On Monday, September 10, 2001 2:24, James Reeves wrote:
> Check the new updated CVS for the new code fixes.

Okay, it works now.

$ ./install-log moo-1.1.tar.bz2
name=moo
version=1.1
extension=tar.bz2
$

Giving it weird names will segfault it, though, but I'm sure you knew that.

I came across another weird package name: "mosfet-liquid0.5.1.tar.gz"  I just 
emailed mosfet to ask why he chose to not put the obligatory - between the d 
and the 0.

-- 
Andy Goth  |  unu...@op...  |  http://null.cc.uic.edu/~andy/

Re: [ID] Hey

[Andy G. <unu...@op...>]

On Monday, September 10, 2001 2:24, James Reeves wrote:
> On Mon, Sep 10, 2001 at 01:55:01PM -0500, Andy Goth wrote:
> I think it was fairly late when I was coding that... oops! Just spotted
> something:
> 	void get_package_info(const char*, char*, char*, char*);
>
> *should* be:
> 	void get_package_info(const char*, char**, char**, char**);

Okay, I think I'm getting it...

> I don't understand how it could have worked in the first place on my
> machine! Oh crap, now I see. Damn, I was *really* out of it when I wrote
> this; whilst two wrongs may not make a right, two errors seem to make
> something which appear to have worked for me.
>
> Basically I didn't assign the pointers properly; the only reason it
> displayed right for me was that I had:
> 	printf("name=%s\nversion=%s\nextension=%s\n");
>
> Instead of:
> 	printf("name=%s\nversion=%s\nextension=%s\n", name, version, extension);

Oh, my word... I didn't see that either.  That is the WEIRDEST code I've 
seen.  Hey, try this...

char* extension; /* Reverse order */
char* version;
char* name;
...
printf("name=%s\nversion=%s\nextension=%s\n");

*You* will probably wind up with:

name=tar.bz2
version=1.0
extension=moo

Hehehe.

> Excuse me whilst I repeatedly whack my head against the wall for being so
> stupid. On the plus side, the rest of the code worked :)

Don't hurt yourself more than necessary.

> Check the new updated CVS for the new code fixes.

Okay.
-- 
Andy Goth  |  unu...@op...  |  http://null.cc.uic.edu/~andy/

Re: [ID] Hey

[James R. <jr...@fu...>]

On Mon, Sep 10, 2001 at 01:55:01PM -0500, Andy Goth wrote:
> > That's weird. I wonder if I've made a mistake with setting the memory up
> > correctly for the string. Lemme look into this, but as I say, they worked
> > fine on my machine so it might be easier for you to find the mistake (sorry
> > to dump it on you like this!).
> 
> I tried deciphering what you were doing, but I didn't get it.  I'll try 
> again, later.

It's not exactly the nicest code in the world...

> > > Perhaps I'm doing something wrong.  Anyway, I found one verifiable bug
> > > and fixed it.  It's in cvs.
> >
> > Ok.
> 
> This bug alone makes me question the reality of your successful run.  I mean, 
> it looks quite serious.  You use "char" instead of "char*"!  Twice!!  I guess 
> the only reason it worked for you is that gcc was setting aside four bytes of 
> memory for each char.

I think it was fairly late when I was coding that... oops! Just spotted
something:
	void get_package_info(const char*, char*, char*, char*);

*should* be:
	void get_package_info(const char*, char**, char**, char**);

I don't understand how it could have worked in the first place on my machine!
Oh crap, now I see. Damn, I was *really* out of it when I wrote this; whilst
two wrongs may not make a right, two errors seem to make something which appear
to have worked for me.

Basically I didn't assign the pointers properly; the only reason it displayed
right for me was that I had:
	printf("name=%s\nversion=%s\nextension=%s\n");

Instead of:
	printf("name=%s\nversion=%s\nextension=%s\n", name, version, extension);

Excuse me whilst I repeatedly whack my head against the wall for being so
stupid. On the plus side, the rest of the code worked :)

Check the new updated CVS for the new code fixes.

-- 
James Reeves (Shade)
http://www.arevol.co.uk/

Re: [ID] Hey

[Andy G. <unu...@op...>]

On Monday, September 10, 2001 5:59, you wrote:
> On Sun, Sep 09, 2001 at 01:25:57PM -0500, Andy Goth wrote:
> > Sorry about my inactivity.  I don't always feel up to coding.
>
> I'm the same, although recently I've been coding quite a bit on a small
> patch for another program, which is nearly finished now :)

What works best for me is poking into other people's projects.  That way the 
result looks the most spectacular, especially since people appreciate it 
immediately.  If I finish install-log and make it Wonderful, it'll still be a 
while before people start saying Cool.  But then again... you found me, even 
though install-log.sh was all that was available...

> That's weird. I wonder if I've made a mistake with setting the memory up
> correctly for the string. Lemme look into this, but as I say, they worked
> fine on my machine so it might be easier for you to find the mistake (sorry
> to dump it on you like this!).

I tried deciphering what you were doing, but I didn't get it.  I'll try 
again, later.

> > Perhaps I'm doing something wrong.  Anyway, I found one verifiable bug
> > and fixed it.  It's in cvs.
>
> Ok.

This bug alone makes me question the reality of your successful run.  I mean, 
it looks quite serious.  You use "char" instead of "char*"!  Twice!!  I guess 
the only reason it worked for you is that gcc was setting aside four bytes of 
memory for each char.

-- 
Andy Goth  |  unu...@op...  |  http://null.cc.uic.edu/~andy/

Re: [ID] Hey

[James R. <jr...@fu...>]

On Sun, Sep 09, 2001 at 01:25:57PM -0500, Andy Goth wrote:
> Sorry about my inactivity.  I don't always feel up to coding.

I'm the same, although recently I've been coding quite a bit on a small patch
for another program, which is nearly finished now :)

> I looked at your modifications, and I'm wondering whether or not they worked 
> on your computer.  They don't here. ;^)
> 
> $ ./install-log moo-1.1.tar.bz2
> name=????????
> version=??]??v
> extension=???@p?
> $

I get:

$ ./install-log moo-1.1.tar.bz2
name=moo
version=1.1
extension=tar.bz2
$

That's weird. I wonder if I've made a mistake with setting the memory up
correctly for the string. Lemme look into this, but as I say, they worked fine
on my machine so it might be easier for you to find the mistake (sorry to dump
it on you like this!).

> Perhaps I'm doing something wrong.  Anyway, I found one verifiable bug and 
> fixed it.  It's in cvs.

Ok.

-- 
James Reeves (Shade)
http://www.arevol.co.uk/

[ID] Hey

[Andy G. <unu...@op...>]

Sorry about my inactivity.  I don't always feel up to coding.

I looked at your modifications, and I'm wondering whether or not they worked 
on your computer.  They don't here. ;^)

$ ./install-log moo-1.1.tar.bz2
name=„úÿ¿’úÿ¿
version=‰ì]Ív
extension=´Ðƒ@pÓ
$

Perhaps I'm doing something wrong.  Anyway, I found one verifiable bug and 
fixed it.  It's in cvs.
-- 
Andy Goth  |  unu...@op...  |  http://null.cc.uic.edu/~andy/

Re: [ID] get_package_info function

[Andy G. <unu...@op...>]

On Monday, August 27, 2001 4:36, you wrote:
> Done it, though let's just say I'm glad this'll only be temporary function
> (as it's pretty crap :).

I'll get the cvs.  Got it!  I'll read it later, using the colorful web 
interface.

> I wasn't sure what to do the extensions though;
> checking to see if it has two parts (e.g. .tar.gz) or one (e.g .zip),
> seemed a bit much for a temporary parser, especially since we're assuming a
> tarball anyway. So the extension's outputted as a raw string at the minute,
> though it'll probably be a speciifically assigned number later on, as the
> #defines in package.c seem to suggest.

Sure, treat it as one string.  Search against a database.  And hope nobody 
tries to get extra compression with a .tar.gz.gz. ;^)

> No problem with the version or name
> though, within the limits of the design :)

I'll look.

Thank you very much for your contribution.

-- 
Andy Goth  |  unu...@op...  |  http://sevatech.com/~andy/

[ID] get_package_info function

[James R. <jr...@fu...>]

Done it, though let's just say I'm glad this'll only be temporary function (as
it's pretty crap :). I wasn't sure what to do the extensions though; checking
to see if it has two parts (e.g. .tar.gz) or one (e.g .zip), seemed a bit much
for a temporary parser, especially since we're assuming a tarball anyway. So
the extension's outputted as a raw string at the minute, though it'll probably
be a speciifically assigned number later on, as the #defines in package.c seem
to suggest. No problem with the version or name though, within the limits of
the design :)

-- 
James Reeves (Shade)
http://www.arevol.co.uk/

Re: [ID] PackageInfo

[Andy G. <unu...@op...>]

> Oh, and the extensions probably should have the relevant programs by them,
> so that if there's a compression/archiving format that we forget, it can be
> easily added in. I can't think of a good format to put this in the config
> file though. We would have to put the extension, followed by the unpack
> command. Something like
>
> EXTENSIONS = tar.gz, "tar -xzf %p" : tar.bz2, "tar -xyf %p"

Or we could extend the format to make this clean.

> > > The %n name field will be tricky though, as a name might include a '-'
> > > anyway, like install-log for instance :). I think it would have to be
> > > matched last, with an "anything that's left policy":
> >
> > Parse from the right.
>
> Yeah, I suppose so...

Looking forward (because I for some reason am parsing THIS LETTER from the 
end), I see that some of my worries are once again handled by doing this.

> > > Tell me what you think of this parsing idea then.
> >
> > It'll be durned hard, but if we parse from the right, then the
> > "install-log" program is solved.  I don't believe I've ever seen the
> > package name anywhere other than the beginning.
> >
> > Of course there are packages whose names can't quite be derived from the
> > filename (without wetware).  Think about all those djgpp zip files that
> > cram the GNU development environment into msdog's 8.3 handicap.  Or what
> > about ftp://ftp.uu.net/graphics/jpeg/jpegsrc.v6b.tar.gz?
>
> What about having an optional default name option in the config. So if the
> package doesn't include the name (like the Linux kernel patches I seem to
> remember), it'll default to the one in the config. This means that a
> "local" package config for jpeg6b could look like:
>
> NAME=libjpeg
> PATTERN=*.v%V.%e
>
> Everything up to the first '.' is ignored (a * is better than a %i, I
> think),

Good point.  But matching this way still looks somewhat ambiguous.  What if 
the file were named jpegsrc.v1.6b.tar.gz?  Would %V == 1 and %e == 6b.tar.gz? 
 This can possibly be fixed by only allowing valid %e's.

/me hopes no one tries to release a new version of a gzipped single-file 
package after 1.tap and 1.taq but before 1.tas... heh.

> then 'v' is matched, after that is the version (up to the next '.')
> and then the extension.

Capital V because of the b...

Hey, I'm almost inclined to say that version numbers can be compared by 
strcmp, except that 1.9.0 should be "less" than 1.10.0.  I know there are 
already algorithms out there that can handle this sort correctly.  Let's 
borrow one.  Hmm, I know php has one, and do does tcl...

> The name isn't included so the default name is put
> in. Btw, another thought: package specific configs should override global
> configs, although that's pretty obvious :)

> > One, support only tarballs.  This means grab the text from the end up to
> > the "t".  It seems easy...
> >
> > Two, handle the version as a string.  This means grab text from just to
> > the left of the ".tar." to the first "-".  Of course all this is with
> > reference to the END of the string.
> >
> > Three, everything before the "-" is the name.
> >
> > Got it?  It'll work for install-log... that's good enough for now.
>
> Ok, I'm doing it now.

Thanks, bud.  Projects I do all by myself rarely reach completion because 
there's no one to take over when I'm tired.  I promise I'll get back into it 
in a bit.  But for now I feel like focusing a bit more on lighting--something 
that rewards me with pretty graphics when I do things right.  (Want a nifty 
screen shot of an old version?  A still just doesn't do it justice...)

> Unfortunately I'm about to start work on some design
> work for a company, and Uni beckons in October, so there'll probably be
> some reading materal I have to get through in September. In short, I'll
> have less time for install-log, at least in the immediate future.

Aw, you whine too much.  "Uni" starts for me tomorrow, and I'm already 
reading years ahead, just because Pentium u/v weaving and the rs232 protocol 
were too interesting for me to wait. ;^)  Despite all this, I *still* have 
time to worry about the newly-discovered limitations of the randomly-ordered 
vectors I use in lighting.  Not to mention the randomly-ordered source code 
we both use in install-log...

-- 
Andy Goth  |  unu...@op...  |  http://sevatech.com/~andy/

Re: [ID] Linked lists

[James R. <jr...@fu...>]

On Sat, Aug 25, 2001 at 05:24:57PM -0500, Andy Goth wrote:
> Are we happy with our linked lists?  My lighting project requires more 
> advanced lists, and maybe I could bring the code into install-log.
>
> Most likely we don't need this, but keep it in mind.

Will do. I tend to agree - too much functionality for now.
 
> ..
> 
> Oh, heh, I just realized I don't need this much functionality myself!  Since 
> the list doesn't need to be sorted at all, heap, count, capacity, and step 
> are all I need, and heap can just be a void*, pointing to various pieces of 
> data.
> 
> /me goes back to vim to fix this...

Ain't Vim great?

-- 
James Reeves (Shade)
http://www.arevol.co.uk/