Re: How can I trace a segfault on program start?

2001-07-17 Thread Philip Blundell
>Obviously!  But what is causing it?  This happens while the program is
>loading, before any of my own code is executed.

Some buggy constructor in a shared library?

What do you get if you set LD_DEBUG=files before running your program?

p.




pgpKb4wHSOnog.pgp
Description: PGP signature


Re: potato - where's lp

2000-01-19 Thread Philip Blundell
>devices.  Maybe I'm loosing my marbles but I didn't
>remember this connection in the 2.0 kernel config. 
>Also the help calls the parellel device option out for
>things like zip drives etc... not printers in general.
> Is this connection new in 2.2?

Yes, it is new in 2.2.

>Also I thought that there was support for USB in 2.2,
>but I havn't found it in the menu config items (yet). 
>I did select prompt for experimental code.  

I don't think there is any (usable) USB in 2.2.  Upgrade to 2.3 or wait for 
2.4.

p.



Re: kernel panic: vfs: unable to mount root fs install errror 01:00

2002-01-13 Thread Philip Blundell
On Sat, Jan 12, 2002 at 05:56:37PM -0800, justin cunningham wrote:
> I'm trying to get a server built with 2.2r4 potato cd and keep getting
> the above error.  I tried the boot options in f2-f8 and tried mounting
> various root.bins from specifying floppy0 at boot: then got kernel
> panic: no init found try passing init= option to kernel.  I looked up
> the errors on the deb user list and found similar questions but no
> answers.  

Have you tried booting from one of the other CDs?  Each one has a different
kernel, and they don't all work properly for all users.

You might also like to try the woody installer instead.  Nobody is doing
active development on the potato disks any more.

p.



Re: Error with kernel 2.2.5 on Debian

1999-04-09 Thread Philip Blundell
>When booting kernel 2.2.5 under Debian 2.1, I get the error as attached.
>Once booted, everything seems to work fine. I'm guessing this error has

You are probably trying to do `route add 127.0.0.0 dev lo' or something 
similar.  Just remove that line or make it conditional on a 2.0 kernel.  But 
the error is entirely harmless and you can just ignore it if you prefer.

p.