On Wed, 05 Jan 2011 17:31:44 +0100, Karel Klic wrote:
I'm working on a client uploading the whole coredump now.
It would be nice to collect some RTT + bandwidth + core sizes anonymous stats for further decisions. And also how the idea gets accepted wrt security.
so I added the gdbserver possibility to the "Future work" section of the documentation for now.
OK, feel free to ping me for the threading/x86_64-only/whatever extensions later.
Still in none of the cases it completes in 60 seconds after which you kill current GDB. So you are going to be killing even the upload processes.
60 seconds is to generate a backtrace from a coredump. Much more time is usually needed to download and extract debuginfos.
Why is there such hard limit? I wanted to bugreport my local Firefox crash but I could not. I would keep it running longer but I was given no such option.
Wouldn't it make sense to merge your gdbserver code to GDB's gdbserver?
It cannot be merged as I wrote it based on elfutils. FSF gdbserver is based on bfd. bfd supports even non-ELF targets.
elfutils is both faster and easier to write with than bfd. As the primary goal was performance I did not want to risk performance issues on the bfd side. Plus the project was at least attractive using elfutils.
Thanks, Jan