[asterisk-bugs] [JIRA] Updated: (DAHTOOL-59) dahdi_monitor reports error writing wav files

[Richard Miller (JIRA)]

     [ https://issues.asterisk.org/jira/browse/DAHTOOL-59?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Richard Miller updated DAHTOOL-59:
----------------------------------

    Description: 
After hitting control-C when writing a wav file, dahdi_monitor reports
"Failed to read in a full wav header.  Expect bad things."

Also when using the -F output option, the wav header is not written.

There are two possible ways to correct the first problem.
1. Change the fopen mode from "w" to "w+".
2. Don't bother reading in the header as we already have a copy in RAM.

I chose to use method 2 in the patch that will follow.  (It can't be attached when creating the issue.)

The second problem is also corrected in the patch I submitted.


  was:
After hitting control-C when writing a wav file, dahdi_monitor reports
"Failed to read in a full wav header.  Expect bad things."

Also when using the -F output option, the wav header is not written.

There are two possible ways to correct the first problem.
1. Change the fopen mode from "w" to "w+".
2. Don't bother reading in the header as we already have a copy in RAM.

I chose to use method 2 in the patch that will follow.  (It can't be attached when creating the issue.)




> dahdi_monitor reports error writing wav files
> ---------------------------------------------
>
>                 Key: DAHTOOL-59
>                 URL: https://issues.asterisk.org/jira/browse/DAHTOOL-59
>             Project: DAHDI-Tools
>          Issue Type: Bug
>      Security Level: None
>          Components: Utilities
>    Affects Versions: 2.5.0.2, 2.6.0, 2.6.1, 2.6.2
>            Reporter: Richard Miller
>            Assignee: Russ Meyerriecks
>            Severity: Minor
>         Attachments: dahdi_monitor.diff
>
>
> After hitting control-C when writing a wav file, dahdi_monitor reports
> "Failed to read in a full wav header.  Expect bad things."
> Also when using the -F output option, the wav header is not written.
> There are two possible ways to correct the first problem.
> 1. Change the fopen mode from "w" to "w+".
> 2. Don't bother reading in the header as we already have a copy in RAM.
> I chose to use method 2 in the patch that will follow.  (It can't be attached when creating the issue.)
> The second problem is also corrected in the patch I submitted.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira