close
Comments you submit will be routed for moderation. If you have an account, please log in first.
Modify

Opened 19 months ago

Closed 15 months ago

Last modified 15 months ago

#393 closed bug (invalid)

Crash while supposedly running an arexx script in the background.

Reported by: Deniil715 Owned by:
Priority: undecided Milestone:
Component: ARexx interface Version: 2.8
Severity: major Keywords:
Cc: OS Platform:
Blocked By: Blocking:
Release Notes:

Description

I came home from work and YAM had crashed. From the crashlog it appeared to be running an arexx script. I have a script that is runs one a day in the background.

Attachments (2)

Crashlog_YAM_2013-03-11_18-09-52.txt (38.2 KB) - added by Deniil715 19 months ago.
OS4.1.6 Crashlog
DagensTV.rexx (198 bytes) - added by Deniil715 19 months ago.
Script that was running. (The tool DagensTV was not running.)

Download all attachments as: .zip

Change History (10)

Changed 19 months ago by Deniil715

OS4.1.6 Crashlog

Changed 19 months ago by Deniil715

Script that was running. (The tool DagensTV was not running.)

comment:1 Changed 19 months ago by tboeckel

(In [6626]) * rexx/mailinfo.c: added some NULL pointer checks. This refs #393.

comment:2 Changed 19 months ago by tboeckel

  • Milestone set to YAM 2.8p1

This issue is a bit strange. The crashlog clearly points out that the crash happened while YAM was processing the MAILINFO ARexx command. But there is no such call in the script you supplied. Are you sure it was really this script causing the crash?

comment:3 Changed 19 months ago by tboeckel

Perhaps you should adapt your script to make sure that there is actually a mail to be read and analyzed. For example if the current folder is a folder group instead of a real mail folder then there will be no mail to be read and hence cause your script to fail.

comment:4 Changed 18 months ago by tboeckel

  • Status changed from new to pending

Bump! Still waiting for a reply...

comment:5 Changed 18 months ago by trac-robot

  • Status changed from pending to closed

This ticket was closed automatically by the system. It was previously set to a Pending status and hasn't been updated within 14 days.

comment:6 Changed 15 months ago by damato

  • Status changed from closed to reopened

comment:7 Changed 15 months ago by damato

  • Resolution set to invalid
  • Status changed from reopened to closed

comment:8 Changed 15 months ago by damato

  • Milestone YAM 2.8p1 deleted

Add Comment

Modify Ticket

Action
as closed .
The resolution will be deleted. Next status will be 'reopened'.
Author


E-mail address and user name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.

This list contains all users that will be notified about changes made to this ticket.

These roles will be notified: Reporter, Owner, Subscriber

Nobody is currently notified about changes to this ticket.