Re: Add miredo to the default install.

2009-12-16 Thread Alain Kalker
Op maandag 14-12-2009 om 20:29 uur [tijdzone -0500], schreef Daniel
Chen:
> My (perhaps flawed) impression is that many desktop users would not care
> about IPv6.

[irony style="smile"]My (perhaps flawed) impression is that many
consumers would not care about the environment.[/irony]

The trouble is: IPv6 is coming, whether anyone cares or not. IPv4 is
rapidly running out of addresses, so sooner or later we're going to have
to switch. Gently coaxing users to get acquainted with IPv6 is IMO a
much better idea than their ISPs dropping letters in their mailboxes one
day stating "Either switch to IPv6 NOW or lose connectivity."

Just my €0,05

-Alain


-- 
Ubuntu-devel-discuss mailing list
Ubuntu-devel-discuss@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss


Re: Problems using apport-chroot for local crash analysis

2009-11-27 Thread Alain Kalker
Op vrijdag 27-11-2009 om 10:18 uur [tijdzone +0100], schreef Alain
Kalker:
> I would like to use the extensive features of apport to assist with
> local crash analysis, but am running into several problems.

Some minor additions:

I want to do the retracing as a normal user, not as root. Hence the use
of apport-chroot, and also the problem with apport-retrace -R giving an
incomplete stacktrace because it can't install debug symbol packages.
The reason I want to do this is not to spam  with installed
debug symbol packages, and reducing the workload on updates.

[1]: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/487759


-- 
Ubuntu-devel-discuss mailing list
Ubuntu-devel-discuss@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss


Problems using apport-chroot for local crash analysis

2009-11-27 Thread Alain Kalker
I would like to use the extensive features of apport to assist with
local crash analysis, but am running into several problems.

The scenario:

On a network of machines, there is a machine, called , on which
a program crashes. Another machine, , is designated to do crash
analysis, in particular retracing, using apport-chroot.

Because the crashes may involve locally developed or unreleased
packages, they don't necessarily need to be reported to Launchpad.

Problem #1: How do I setup apport to send crash reports to a local
machine and not to Launchpad?

For the sake of argument, let's suppose the crash reports will simply be
copied over to  for analysis.

Problem #2: The report generated right after a crash happens, doesn't
include the required field Package in the report. Only when the user
clicks on "Report Problem", this information is included, including an
incomplete stack trace (see Problem #3), but I want to be able to do
unattended crash reporting.

I reported this problem originally as a bug: LP: #487759 [1], and Martin
Pitt explained that this info isn't collected right after the crash for
performance reasons.
He suggested that I use apport-retrace's -R option to rebuild the crash
report. The problem is that this requires me to also use the -o option.
Unfortunately, this causes apport-retrace to attempt a retrace. Back to
square one (well, Problem #3 actually).

Problem #3: The backtrace from a crash report (even after retracing on
 is incomplete (no function parameters, often even no function
names at all).

When I view a crash report on , it contains an incomplete
stacktrace. Reasonable, as  doesn't have the necessary debugging
symbol packages installed.
But when I analyze a crash on  using apport-chroot in retrace
mode, the stack trace is still incomplete. It seems that (still have to
verify that) apport-chroot/retrace doesn't do a new retrace if the crash
report already contains one.

Any help with this will be greatly appreciated.

Thanks to Martin Pitt for creating such a wonderfully useful tool!

Kind regards,

Alain


-- 
Ubuntu-devel-discuss mailing list
Ubuntu-devel-discuss@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss