On Sun, 2008-01-06 at 01:14 +0100, Juliusz Chroboczek wrote:
> Ya Ziad,
>
Hi...
> > And yes, there's a way: Compile Polipo with debug symbols (by passing
> > "-g" to the compiler, note that by default the compile process will use
> > the debug symbols and you should not do anything more) and don't run
> > "stip" on the resulting binary, then run Polipo like this:
> > gdb polipo
>
> I don't think that Thomas is reporting a crash; he's reporting
> a problem with Polipo shutting down a connection during an upload to
> Ebay. Gdb won't give any useful information about that.
My mistake. I didn't read the message correctly.
>
> I'd really need to get a system call trace in order to debug that.
> And I have no idea what tools can be used on OpenBSD to generate one.
>
> Juliusz
>
Maybe "ktrace"? The discussion (linked below) describe how to get a
system trace using "ktrace -i" and "kdump -l". (I never used OpenBSD
myself.)
Link:
http://monkey.org/openbsd/archive/misc/0212/msg00796.html
Again, sorry for being hasty, I should have read the message more
thoroughly before responding; hopefully no harm done.
Ziyad.
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Polipo-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/polipo-users
