Mailinglist Archive: yast-devel (30 mails)
| < Previous | Next > |
Re: [yast-devel] possible bug report: snapper dumps core
- From: Arvin Schnell <aschnell@xxxxxxx>
- Date: Tue, 5 Feb 2013 10:43:28 +0100
- Message-id: <20130205094328.GA2249@suse.de>
On Tue, Feb 05, 2013 at 07:09:37AM +0100, carsten@xxxxxxxxxxxx wrote:
Thanks for reporting this. I don't have to problem here but I
have found a similar bug
(https://github.com/lodle/Desurium/issues/348). Apparently the
boost thread interface has changed with boost 1.52. Could you try
to integrate this patch:
diff --git a/server/Background.cc b/server/Background.cc
index dfc06e4..eada0e7 100644
--- a/server/Background.cc
+++ b/server/Background.cc
@@ -42,7 +42,9 @@ Backgrounds::Backgrounds()
Backgrounds::~Backgrounds()
{
thread.interrupt();
- thread.join();
+
+ if (thread.joinable())
+ thread.join();
}
Another place to check for thread.joinable() could be
Client::~Client().
If the patch doesn't help could you please open an issue on
github.
Regards,
Arvin
--
Arvin Schnell, <aschnell@xxxxxxx>
Senior Software Engineer, Research & Development
SUSE LINUX Products GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB
16746 (AG Nürnberg)
Maxfeldstraße 5
90409 Nürnberg
Germany
--
To unsubscribe, e-mail: yast-devel+unsubscribe@xxxxxxxxxxxx
To contact the owner, e-mail: yast-devel+owner@xxxxxxxxxxxx
Hey, I'm running snapper on Arch Linux, using lvm thin provisioning for
the snapshots. It seems to be working fine (I can create, mount,
delete,... snapshots). However, after a command completes, some boost
thread seems to die:
what(): boost thread: thread not joinable: Invalid argument
Aborted (core dumped)
Thanks for reporting this. I don't have to problem here but I
have found a similar bug
(https://github.com/lodle/Desurium/issues/348). Apparently the
boost thread interface has changed with boost 1.52. Could you try
to integrate this patch:
diff --git a/server/Background.cc b/server/Background.cc
index dfc06e4..eada0e7 100644
--- a/server/Background.cc
+++ b/server/Background.cc
@@ -42,7 +42,9 @@ Backgrounds::Backgrounds()
Backgrounds::~Backgrounds()
{
thread.interrupt();
- thread.join();
+
+ if (thread.joinable())
+ thread.join();
}
Another place to check for thread.joinable() could be
Client::~Client().
If this is the wrong place for such a report, or, since it's not
suse-related, there is no general interest, please tell me.
If the patch doesn't help could you please open an issue on
github.
Regards,
Arvin
--
Arvin Schnell, <aschnell@xxxxxxx>
Senior Software Engineer, Research & Development
SUSE LINUX Products GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB
16746 (AG Nürnberg)
Maxfeldstraße 5
90409 Nürnberg
Germany
--
To unsubscribe, e-mail: yast-devel+unsubscribe@xxxxxxxxxxxx
To contact the owner, e-mail: yast-devel+owner@xxxxxxxxxxxx
| < Previous | Next > |