Registering for RConnectionMonitor events causes thread to panic

Question

I have a custom observer class derived from CBase, MConnectionMonitorObserver, and QObject(for signals) that I use to observe events from RConnectionMonitor.

When I call the RConnectionMonitor::NotifyEventL passing the observer instance, the application crashes saying that a thread has panicked.

What I'm trying to do here is to listen to the network events asynchronously without blocking the main thread.

EDIT: Should I use an active object to hold the RConnectionMonitor object?

Best regards

This means you are using a bad handle. Are you opening the connection successfully? — James, Aug 15 '11 at 00:54
I can successfully use RConnectionMonitor using the Get*Attribute calls, so I guess my handle should be ok? — Gerstmann, Aug 15 '11 at 05:57
@James It seems that I connected just after i called NotifyEventL, which caused the panic. Please format your comment as an answer so I can accept it. — Gerstmann, Aug 15 '11 at 08:08

score 0 · Accepted Answer · answered Aug 21 '11 at 10:31

0

The problem was, as @James commented, that I was registering for events before I established the connection to the connection monitor server.

answered Aug 21 '11 at 10:31

Gerstmann

5,368
6
37
57

Registering for RConnectionMonitor events causes thread to panic

1 Answers1