abrt 1.1.1 detected a crash.
Attached file: backtrace
comment: I'm trying to debug why FLDIGI will bring X down, so started it with redirection enabled. CTRL-C and it cored.
reason: Process /usr/bin/fldigi was killed by signal 11 (SIGSEGV)
release: Fedora release 13 (Goddard)
How to reproduce
1. Start FLDIGI with output redirected via 2>&1 for debugging
2. Press CTRL-C to quit
3. Watch the core.
Created attachment 423131 [details]
I submitted your report upstream as I was unable to reproduce the bug here. Could you please include the rig you are using with fldigi if you are using CAT control? And if you are using pulseaudio or portaudio.
As many details that you can provide may help allot.
Meanwhile Fldigi 3.20-15 will be submitted to updates-testing shortly. I am test building it as of this report.
Thanks es 73 de Randy N3LRX
Thank you Randy!
Rig control is for a Ten-Tec Orion, and I'm using the Portaudio, but it's setting Pulseaudio as the engine to use.
I'm actually having a lot of trouble with this particular build of Fedora 13 with regards to X- I'm troubleshooting why resizing FLDIGI crashes X. I'm also troubleshooting why X is missing mouse-up events (where "mouse-down" becomes sticky and won't release until some random several seconds of moving it via the track-pad/point stick, and randomly pressing right/left mouse buttons) where I decided to run FLDIGI in this way.
This crash happened whilst FLDIGI was doing normal decoding (PSK31, I believe) and BEFORE the configuration file was saved for the first time.
3.20.15 has been pushed to updates-testing please see if the problem still occurs.
That fixed it- thanks!