Thanks, Murphy, now the page looks much better. :-)
A few comments about the core stuff.
1. On my RedHat 9, the core is generated with the PID attached
(core.nnnnn), so the test you suggest as [ -e core ] would
not found it. Checking [ -e core* ] would fail if more
than one core is around.
Perhaps something like:
ls 2>/dev/null core* | grep -q core\\.\[0-9\]\\+
would be more reliable and, if positive, you can get the most
recent core name with:
ls -t core* | head -1
and go ahead with moving it to a special directory, etc.
2. To load the core into gdb I had to use:
gdb -c core gtk-gnutella
gdb core or gdb -c core would complain:
core: not in executable format: File format not recognized
Hope this helps.
Mihai
> Hey'
>
> I've written a bug report howto for the gtkg web page and I'd appreciate
> any comments and especially corrections. Since I'm not a developer, there
> could be some serious innacurracies. I've attached it here in case
> someone wants to send me a patch and you can see it in context on my test
> version of the the gtkg site:
>
> http://lawnarchy.swimmingnoodle.com/gtk-gnutella/htdocs/index.php?page=bugreport
>
> Once it's been corrected, I'll submit it to guruz for inclusion on the
> real gtkg homepage.
>
> --
> Murphy
-------------------------------------------------------
This SF.Net email is sponsored by: INetU
Attention Web Developers & Consultants: Become An INetU Hosting Partner.
Refer Dedicated Servers. We Manage Them. You Get 10% Monthly Commission!
INetU Dedicated Managed Hosting http://www.inetu.net/partner/index.php
_______________________________________________
Gtk-gnutella-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/gtk-gnutella-devel
