Opened 15 months ago

Last modified 10 months ago

#2187 new defect

Absolute Timed Events -> Event plugin dies

Reported by: davegravy@… Owned by:
Priority: normal Milestone: 1204
Component: Events Version: 1004
Severity: normal Keywords: event, absolute, timed


If I try to create an absolute timed event, when I reload router, the event plugin device appears to die. Attached is DCERouter.log

Attachments (1)

DCERouter.log (130.7 KB) - added by davegravy@… 15 months ago.
log of router reload after creating absolute timed event

Download all attachments as: .zip

Change History (5)

Changed 15 months ago by davegravy@…

log of router reload after creating absolute timed event

comment:1 Changed 11 months ago by phenigma

um, yeah. so there is no handler for absolute timed events, which results in an unitialized variable and undefined results. Need to set m_tTime to the proper value in Event_Plugin.cpp @line 182.

comment:2 Changed 11 months ago by tschak

Can I get a core dump to cross reference?


comment:3 Changed 11 months ago by tschak

Also, looks like the line you're referencing isn't lining up, can I get more info so I can squash this?


comment:4 Changed 10 months ago by phenigma

TimedEvent?.cpp , not Event_Plugin.cpp. I *think* that is where things lie, but I really haven't had a chance to check it out. I don't have a core dump but you can probably get one by setting an absolute timed event. I tried it once and it's easily reproduceable.

Note: See TracTickets for help on using tickets.