On Fri, 2008-01-04 at 19:35 +0100, Thomas Wiesel wrote:
> bon jour polipo-users,
Hi...
>
> i have some additional infos concerning the ebay-picture-upload-issue:
>
> - a fresh direct compiled darcs get shows the same problem
> --> it seems not to be caused by my openbsd-port
>
> - other uploads work fine (e.g. attachments to web.de email, please find my
> config attached)
>
> - i tested other configurations (e.g. with disk cache, disabling transparent
> cache), did not solve
>
> is there a way to log more output (beside loglevel, which is already #ff)?
(That should be "0xff" not "#ff", but I'm sure it was a typo since
Polipo won't start with that.)
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
(you'll need "gdb" (which is the "GNU Debugger") installed on your
system)
Within "gdb" type:
run argumants
where "arguments" are anything you normally passes to Polipo. For
example:
run logLevel=0xFF logFile="polipo.log" proxyOffline=false
whenever Polipo crashes it will display a lot of information, like what
function it was running when the crash occurred, and to which
application/library it belongs.
You could also type "bt" at the "gdb" prompt to get the "Back Trace"
which is useful.
>
> again, same thing with direct internet connection works fine ....
>
> any ideas how to fix this are welcome :-)
>
> thomas
>
>
>
Hope this helps.
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
