Date   
Re: Shortwave Radiogram all-Olivia-64-2000 transmission this weekend

Al Massaro
 

Decode was good in NW NM DM66, couple of hiccups but nothing major.
AL M
KF5SMH

Re: Shortwave Radiogram all-Olivia-64-2000 transmission this weekend

kd9xb
 

Thanks for the reports!

My reception and decode via Tasmania deteriorated during the half hour.

Direct to my Virginia QTH, it improved.

A worthwhile experiment.  I might try it again next weekend with other robust modes, such as MFSK8.  Or go *very* slow with Olivia 128-2000.

Kim
KD9XB

Re: IC-7300 Internal Sound Card

NU3Q
 

Put radio in digital mode 1st

Sent from my iPhone

On Nov 26, 2017, at 5:49 PM, Mark Dallner <mark@...> wrote:

Anybody out there that is working to setup the FLDigi suite with the internal sound card on the IC-7300?

Thought I check again to see if anyone new had joined the group that is working with the IC-7300 & digital modes.

73
Mark
KD9EEE

Re: IC-7300 Internal Sound Card

Mark Dallner
 

The radio is in digital mode. What the issue is, is getting the radio and and FLRig to talk to each other. Comm port & speed are set correctly on each end.

I am receiving just fine. Keying the 7300 is a maze of an adventure. Tried FLrig and it would dead key the 7300.

Then there is shutting everything off. reloading the programs and it works! Bunch of FM if you ask me. and I don’t mean frequency modulation.

Now to copy all the settings so the next time it decides not to work, I have somewhere to start.

73,
Mark
KD9EEE

Re: IC-7300 Internal Sound Card

Ed W3NR
 

On Sun, 26 Nov 2017 19:11:26 -0600
"Mark Dallner" <mark@...> wrote:

The radio is in digital mode. What the issue is, is getting the radio
and and FLRig to talk to each other. Comm port & speed are set
correctly on each end.

I am receiving just fine. Keying the 7300 is a maze of an adventure.
Tried FLrig and it would dead key the 7300.

Then there is shutting everything off. reloading the programs and it
works! Bunch of FM if you ask me. and I don’t mean frequency
modulation.

Now to copy all the settings so the next time it decides not to work,
I have somewhere to start.

73,
Mark
KD9EEE

Sounds like RFI to me. Reinstalling proves nothing. You only need to
delete the prefs file.

Ed w3NR

Re: IC-7300 Internal Sound Card

Mark Dallner
 

What I meant by reloading was shutting the program down and restarting the program.

I was imprecise in the terms I used.

It works and I don’t really want to mess with it.

Mark
KD9EEE

Re: Shortwave Radiogram, 18-19 Nov, includes 8PSK-500F and -1000F

Paul Newman
 

Hi, Kim.

The band rolled off very rapidly here in Richardson, Texas (EM12px) shortly before the 2330 UTC SWRG transmission.  So, no decode.  Let’s try again, perhaps on a different time slot.

Thank you and 73,

Paul — KA5TYW


On Nov 17, 2017, at 16:35, kd9xb <kimelli@...> wrote:

Shortwave Radiogram this weekend is mostly in the usual MFSK32, but one news story is transmitted first in 8PSK-500F (1690 wpm) and then in 8PSK-1000F (3386 wpm). These modes are probably too fast for HF, but we'll try them anyway.

Details and schedule:

http://swradiogram.net/post/167598577657/shortwave-radiogram-18-19-november-2017-fast

Over the weekend, see listeners' results by visiting https://twitter.com/swradiogram  (Twitter account not required.)

Kim
KD9XB

Re: Shortwave Radiogram all-Olivia-64-2000 transmission this weekend

Paul Newman
 

Hi, Kim.

The band rolled off very rapidly here in Richardson, Texas (EM12px) shortly before the 2330 UTC SWRG transmission.  So, no decode.  Let’s try again, perhaps on a different time slot.

Thank you and 73,

Paul — KA5TYW

On Nov 26, 2017, at 16:26, kd9xb <kimelli@...> wrote:

The Olivia 64-2000 experiment is soon at 2330Z -- 6:30 pm EST -- on 11580 kHz from WRMI Florida.

Wishing you bad reception (otherwise the experiment won't be very interesting).

Kim
KD9XB

Flamp Segment Fault using Script

W. T. Jones
 

The usual info:
Fldigi 4.0.12
Flamp 2.2.03
Ubuntu 16.04 LTS up to date with patches.

I use Flamp to send a Sunday Night Bulletin to our County's ARES membership. The bulletin is in HTML format. Last January I decided to dive into the Flamp Scripts so that I didn't have to sit and watch the computer while it sent the bulletins. It has been working rather well until 2 months ago. When the time happens to kick off the Flamp at 0200Z Flamp segment faults. The worst part of it is that it is not happening consistently. 3 weeks ago it worked. The past 2 weeks including tonight it faulted. I have been trying to figure it out for 2 months without much success.

Here is a sample of the segment faults:
Sep 24 21:15:00 secaprs kernel: [ 2694.155293] flamp[3038]: segfault at 8 ip 00007fe3fd20d36e sp 00007ffc386a0920 error 4 in libstdc++.so.6.0.21[7fe3fd0ee000+172000]
Oct  1 21:15:00 secaprs kernel: [  991.653993] flamp[2524]: segfault at 8 ip 00007f51f06be36e sp 00007fff0b6cab40 error 4 in libstdc++.so.6.0.21[7f51f059f000+172000]
Oct  1 21:15:00 secaprs ntpd[1191]: 204.2.134.162 local addr 192.168.60.50 -> <null>
Oct 15 21:15:00 secaprs kernel: [48086.239836] flamp[8674]: segfault at 8 ip 00007faea86e636e sp 00007ffcd8dd83b0 error 4 in libstdc++.so.6.0.21[7faea85c7000+172000]
Oct 15 21:15:10 secaprs kernel: [48096.828457] perf interrupt took too long (5003 > 5000), lowering kernel.perf_event_max_sample_rate to 25000
Oct 21 14:37:00 secaprs kernel: [ 6854.113233] flamp[4324]: segfault at 8 ip 00007f03736da36e sp 00007ffc7a8f74b0 error 4 in libstdc++.so.6.0.21[7f03735bb000+172000]
Oct 21 14:39:00 secaprs kernel: [ 6974.574189] flamp[4595]: segfault at 8 ip 00007f20a60e336e sp 00007ffcde5d2a40 error 4 in libstdc++.so.6.0.21[7f20a5fc4000+172000]
Nov 26 21:00:00 secaprs kernel: [ 9330.602498] flamp[3645]: segfault at 8 ip 00007f77ca99736e sp 00007ffe78c08390 error 4 in libstdc++.so.6.0.21[7f77ca878000+172000]
Nov 26 21:02:00 secaprs kernel: [ 9450.500065] flamp[3729]: segfault at 8 ip 00007f01b64d436e sp 00007ffffb687460 error 4 in libstdc++.so.6.0.21[7f01b63b5000+172000]

Attached is the script and the bulletin for tonight. Any ideas would be helpful as to what I am doing wrong.





Regards,

WT
Real heroes do not wear capes. They wear dog tags, turnout gear, and badges!

Re: Flamp Segment Fault using Script

Mike P.
 

WT, I am surmising that the only thing that is
changing is the size of the file(s) that you have
been sending. If the current file sizes are larger
than before, perhaps the scheduled transmissions
are stepping on each other before the prior one
has finished.

Try spacing out your EVENT TIMES and see if
that helps. I'm not sure if that is the problem but
I would be interested to know how you fare.

73

--- Mike Pompey, AE7XB
Port Orchard, Washington state

On 26 Nov 2017 at 21:54, W. T. Jones wrote:


The usual info:
Fldigi 4.0.12
Flamp 2.2.03
Ubuntu 16.04 LTS up to date with patches.

I use Flamp to send a Sunday Night Bulletin to our County's ARES membership. The bulletin is
in HTML format. Last January I decided to dive into the Flamp Scripts so that I didn't have to sit
and watch the computer while it sent the bulletins. It has been working rather well until 2 months
ago. When the time happens to kick off the Flamp at 0200Z Flamp segment faults. The worst
part of it is that it is not happening consistently. 3 weeks ago it worked. The past 2 weeks
including tonight it faulted. I have been trying to figure it out for 2 months without much success.

Here is a sample of the segment faults:
Sep 24 21:15:00 secaprs kernel: [ 2694.155293] flamp[3038]: segfault at 8 ip 00007fe3fd20d36e
sp 00007ffc386a0920 error 4 in libstdc++.so.6.0.21[7fe3fd0ee000+172000]
Oct  1 21:15:00 secaprs kernel: [  991.653993] flamp[2524]: segfault at 8 ip 00007f51f06be36e
sp 00007fff0b6cab40 error 4 in libstdc++.so.6.0.21[7f51f059f000+172000]
Oct  1 21:15:00 secaprs ntpd[1191]: 204.2.134.162 local addr 192.168.60.50 -> <null>
Oct 15 21:15:00 secaprs kernel: [48086.239836] flamp[8674]: segfault at 8 ip 00007faea86e636e
sp 00007ffcd8dd83b0 error 4 in libstdc++.so.6.0.21[7faea85c7000+172000]
Oct 15 21:15:10 secaprs kernel: [48096.828457] perf interrupt took too long (5003 > 5000),
lowering kernel.perf_event_max_sample_rate to 25000
Oct 21 14:37:00 secaprs kernel: [ 6854.113233] flamp[4324]: segfault at 8 ip 00007f03736da36e
sp 00007ffc7a8f74b0 error 4 in libstdc++.so.6.0.21[7f03735bb000+172000]
Oct 21 14:39:00 secaprs kernel: [ 6974.574189] flamp[4595]: segfault at 8 ip 00007f20a60e336e
sp 00007ffcde5d2a40 error 4 in libstdc++.so.6.0.21[7f20a5fc4000+172000]
Nov 26 21:00:00 secaprs kernel: [ 9330.602498] flamp[3645]: segfault at 8 ip 00007f77ca99736e
sp 00007ffe78c08390 error 4 in libstdc++.so.6.0.21[7f77ca878000+172000]
Nov 26 21:02:00 secaprs kernel: [ 9450.500065] flamp[3729]: segfault at 8 ip 00007f01b64d436e
sp 00007ffffb687460 error 4 in libstdc++.so.6.0.21[7f01b63b5000+172000]

Attached is the script and the bulletin for tonight. Any ideas would be helpful as to what I am
doing wrong.




Regards,

WT
Real heroes do not wear capes. They wear dog tags, turnout gear, and badges!



Electronics usually stop working once the magic smoke is released.

Re: Flamp Segment Fault using Script

Dave
 

Are you familiar with running a program using the gnu debugger, gdb?

I suggest you try repeating your broadcast (use a dummy load), but using gdb.

$ cd flamp-2.2.03
$ ./configure && make
$ gdb src/flamp
(gdb) handle SIGUSR2 nostop
(gdb) run

when the program seg faults it will return you to the gdb prompt.  Use the backtrace command to ascertain where in the program the seg fault has occurred.

(gdb) bt

Submit the results of the backtrace to Robert, KK5VD, and myself, W1HKJ at the cc: addresses of this reply.

73, David, W1HKJ

On 11/26/2017 08:54 PM, W. T. Jones wrote:
The usual info:
Fldigi 4.0.12
Flamp 2.2.03
Ubuntu 16.04 LTS up to date with patches.

I use Flamp to send a Sunday Night Bulletin to our County's ARES membership. The bulletin is in HTML format. Last January I decided to dive into the Flamp Scripts so that I didn't have to sit and watch the computer while it sent the bulletins. It has been working rather well until 2 months ago. When the time happens to kick off the Flamp at 0200Z Flamp segment faults. The worst part of it is that it is not happening consistently. 3 weeks ago it worked. The past 2 weeks including tonight it faulted. I have been trying to figure it out for 2 months without much success.

Here is a sample of the segment faults:
Sep 24 21:15:00 secaprs kernel: [ 2694.155293] flamp[3038]: segfault at 8 ip 00007fe3fd20d36e sp 00007ffc386a0920 error 4 in libstdc++.so.6.0.21[7fe3fd0ee000+172000]
Oct  1 21:15:00 secaprs kernel: [  991.653993] flamp[2524]: segfault at 8 ip 00007f51f06be36e sp 00007fff0b6cab40 error 4 in libstdc++.so.6.0.21[7f51f059f000+172000]
Oct  1 21:15:00 secaprs ntpd[1191]: 204.2.134.162 local addr 192.168.60.50 -> <null>
Oct 15 21:15:00 secaprs kernel: [48086.239836] flamp[8674]: segfault at 8 ip 00007faea86e636e sp 00007ffcd8dd83b0 error 4 in libstdc++.so.6.0.21[7faea85c7000+172000]
Oct 15 21:15:10 secaprs kernel: [48096.828457] perf interrupt took too long (5003 > 5000), lowering kernel.perf_event_max_sample_rate to 25000
Oct 21 14:37:00 secaprs kernel: [ 6854.113233] flamp[4324]: segfault at 8 ip 00007f03736da36e sp 00007ffc7a8f74b0 error 4 in libstdc++.so.6.0.21[7f03735bb000+172000]
Oct 21 14:39:00 secaprs kernel: [ 6974.574189] flamp[4595]: segfault at 8 ip 00007f20a60e336e sp 00007ffcde5d2a40 error 4 in libstdc++.so.6.0.21[7f20a5fc4000+172000]
Nov 26 21:00:00 secaprs kernel: [ 9330.602498] flamp[3645]: segfault at 8 ip 00007f77ca99736e sp 00007ffe78c08390 error 4 in libstdc++.so.6.0.21[7f77ca878000+172000]
Nov 26 21:02:00 secaprs kernel: [ 9450.500065] flamp[3729]: segfault at 8 ip 00007f01b64d436e sp 00007ffffb687460 error 4 in libstdc++.so.6.0.21[7f01b63b5000+172000]

Attached is the script and the bulletin for tonight. Any ideas would be helpful as to what I am doing wrong.





Regards,

WT
Real heroes do not wear capes. They wear dog tags, turnout gear, and badges!

Re: Flamp Segment Fault using Script

Dave
 

I see that the cc: addressees did not make it through groups.io ... that is a good thing.

w1hkj [at] bellsouth [dot] net
kk5vd [at] yahoo [dot] com

On 11/26/2017 11:53 PM, Dave wrote:
Are you familiar with running a program using the gnu debugger, gdb?

I suggest you try repeating your broadcast (use a dummy load), but using gdb.

$ cd flamp-2.2.03
$ ./configure && make
$ gdb src/flamp
(gdb) handle SIGUSR2 nostop
(gdb) run

when the program seg faults it will return you to the gdb prompt.  Use the backtrace command to ascertain where in the program the seg fault has occurred.

(gdb) bt

Submit the results of the backtrace to Robert, KK5VD, and myself, W1HKJ at the cc: addresses of this reply.

73, David, W1HKJ

On 11/26/2017 08:54 PM, W. T. Jones wrote:
The usual info:
Fldigi 4.0.12
Flamp 2.2.03
Ubuntu 16.04 LTS up to date with patches.

I use Flamp to send a Sunday Night Bulletin to our County's ARES membership. The bulletin is in HTML format. Last January I decided to dive into the Flamp Scripts so that I didn't have to sit and watch the computer while it sent the bulletins. It has been working rather well until 2 months ago. When the time happens to kick off the Flamp at 0200Z Flamp segment faults. The worst part of it is that it is not happening consistently. 3 weeks ago it worked. The past 2 weeks including tonight it faulted. I have been trying to figure it out for 2 months without much success.

Here is a sample of the segment faults:
Sep 24 21:15:00 secaprs kernel: [ 2694.155293] flamp[3038]: segfault at 8 ip 00007fe3fd20d36e sp 00007ffc386a0920 error 4 in libstdc++.so.6.0.21[7fe3fd0ee000+172000]
Oct  1 21:15:00 secaprs kernel: [  991.653993] flamp[2524]: segfault at 8 ip 00007f51f06be36e sp 00007fff0b6cab40 error 4 in libstdc++.so.6.0.21[7f51f059f000+172000]
Oct  1 21:15:00 secaprs ntpd[1191]: 204.2.134.162 local addr 192.168.60.50 -> <null>
Oct 15 21:15:00 secaprs kernel: [48086.239836] flamp[8674]: segfault at 8 ip 00007faea86e636e sp 00007ffcd8dd83b0 error 4 in libstdc++.so.6.0.21[7faea85c7000+172000]
Oct 15 21:15:10 secaprs kernel: [48096.828457] perf interrupt took too long (5003 > 5000), lowering kernel.perf_event_max_sample_rate to 25000
Oct 21 14:37:00 secaprs kernel: [ 6854.113233] flamp[4324]: segfault at 8 ip 00007f03736da36e sp 00007ffc7a8f74b0 error 4 in libstdc++.so.6.0.21[7f03735bb000+172000]
Oct 21 14:39:00 secaprs kernel: [ 6974.574189] flamp[4595]: segfault at 8 ip 00007f20a60e336e sp 00007ffcde5d2a40 error 4 in libstdc++.so.6.0.21[7f20a5fc4000+172000]
Nov 26 21:00:00 secaprs kernel: [ 9330.602498] flamp[3645]: segfault at 8 ip 00007f77ca99736e sp 00007ffe78c08390 error 4 in libstdc++.so.6.0.21[7f77ca878000+172000]
Nov 26 21:02:00 secaprs kernel: [ 9450.500065] flamp[3729]: segfault at 8 ip 00007f01b64d436e sp 00007ffffb687460 error 4 in libstdc++.so.6.0.21[7f01b63b5000+172000]

Attached is the script and the bulletin for tonight. Any ideas would be helpful as to what I am doing wrong.





Regards,

WT
Real heroes do not wear capes. They wear dog tags, turnout gear, and badges!


Re: Experience and guidance on tablet operation under Linux v. Windows?

rgireson
 

Thanks to all for your comments and suggestions.  The linux experience matches my own from a few years back on a dual boot machine - software seems to run a bit more slowly.  My benchmarks were for the same code compiled under Visual FORTRAN (XP) and a linux compiler.  For heavily CPU-intensive floating point code, the linux version ran about 50% more slowly.  Could be more compiler optimization options than the OS itself, but hard to tell.

The good news - I solved my primary problem in Windows, which was the inability of the tablet to copy or send images, even in MFSK64 x1.  It didn't make sense to me that an Android phone can handle that, but not the tablet.  Figured it was likely overhead and competition for CPU cycles, so I went into Task Manager and bumped the priority to High for the fldigi.exe process.  Now works fine.  I now start it from a .bat file that automatically sets CPU priority when invoked:
   start "fldigi-4.0.4" /high "C:\Program Files\Fldigi-4.0.4\fldigi.exe"

73,
Rob K6RGI

Re: Flamp Segment Fault using Script

W. T. Jones
 

Dave,

I can do that and we'll see where it takes things.

Thank you for the instructions. I did get the email addresses in the follow on message.



Regards,

WT
Real heroes do not wear capes. They wear dog tags, turnout gear, and badges!

On Mon, Nov 27, 2017 at 12:53 AM, Dave <w1hkj@...> wrote:
Are you familiar with running a program using the gnu debugger, gdb?

I suggest you try repeating your broadcast (use a dummy load), but using gdb.

$ cd flamp-2.2.03
$ ./configure && make
$ gdb src/flamp
(gdb) handle SIGUSR2 nostop
(gdb) run

when the program seg faults it will return you to the gdb prompt.  Use the backtrace command to ascertain where in the program the seg fault has occurred.

(gdb) bt

Submit the results of the backtrace to Robert, KK5VD, and myself, W1HKJ at the cc: addresses of this reply.

73, David, W1HKJ

On 11/26/2017 08:54 PM, W. T. Jones wrote:
The usual info:
Fldigi 4.0.12
Flamp 2.2.03
Ubuntu 16.04 LTS up to date with patches.

I use Flamp to send a Sunday Night Bulletin to our County's ARES membership. The bulletin is in HTML format. Last January I decided to dive into the Flamp Scripts so that I didn't have to sit and watch the computer while it sent the bulletins. It has been working rather well until 2 months ago. When the time happens to kick off the Flamp at 0200Z Flamp segment faults. The worst part of it is that it is not happening consistently. 3 weeks ago it worked. The past 2 weeks including tonight it faulted. I have been trying to figure it out for 2 months without much success.

Here is a sample of the segment faults:
Sep 24 21:15:00 secaprs kernel: [ 2694.155293] flamp[3038]: segfault at 8 ip 00007fe3fd20d36e sp 00007ffc386a0920 error 4 in libstdc++.so.6.0.21[7fe3fd0ee000+172000]
Oct  1 21:15:00 secaprs kernel: [  991.653993] flamp[2524]: segfault at 8 ip 00007f51f06be36e sp 00007fff0b6cab40 error 4 in libstdc++.so.6.0.21[7f51f059f000+172000]
Oct  1 21:15:00 secaprs ntpd[1191]: 204.2.134.162 local addr 192.168.60.50 -> <null>
Oct 15 21:15:00 secaprs kernel: [48086.239836] flamp[8674]: segfault at 8 ip 00007faea86e636e sp 00007ffcd8dd83b0 error 4 in libstdc++.so.6.0.21[7faea85c7000+172000]
Oct 15 21:15:10 secaprs kernel: [48096.828457] perf interrupt took too long (5003 > 5000), lowering kernel.perf_event_max_sample_rate to 25000
Oct 21 14:37:00 secaprs kernel: [ 6854.113233] flamp[4324]: segfault at 8 ip 00007f03736da36e sp 00007ffc7a8f74b0 error 4 in libstdc++.so.6.0.21[7f03735bb000+172000]
Oct 21 14:39:00 secaprs kernel: [ 6974.574189] flamp[4595]: segfault at 8 ip 00007f20a60e336e sp 00007ffcde5d2a40 error 4 in libstdc++.so.6.0.21[7f20a5fc4000+172000]
Nov 26 21:00:00 secaprs kernel: [ 9330.602498] flamp[3645]: segfault at 8 ip 00007f77ca99736e sp 00007ffe78c08390 error 4 in libstdc++.so.6.0.21[7f77ca878000+172000]
Nov 26 21:02:00 secaprs kernel: [ 9450.500065] flamp[3729]: segfault at 8 ip 00007f01b64d436e sp 00007ffffb687460 error 4 in libstdc++.so.6.0.21[7f01b63b5000+172000]

Attached is the script and the bulletin for tonight. Any ideas would be helpful as to what I am doing wrong.





Regards,

WT
Real heroes do not wear capes. They wear dog tags, turnout gear, and badges!


Re: Flamp Segment Fault using Script

W. T. Jones
 

Mike,

Thanks for the comment and suggestion. I just checked the file sizes for the past year. Largest was 48K and smallest was 29K. The file this Sunday was right in the middle at 37K. I am going to keep the timing as is right now because Dave chimed in with a suggestion on how to trace the segfault. I am going to do that before I change anything since that may mask the problem for Dave and the Developers.

Again thanks mike and I will report the results of the investigation.


Regards,

WT
Real heroes do not wear capes. They wear dog tags, turnout gear, and badges!

On Sun, Nov 26, 2017 at 11:13 PM, Mike P. <ae7xb@...> wrote:

WT, I am surmising that the only thing that is
changing is the size of the file(s) that you have
been sending.  If the current file sizes are larger
than before, perhaps the scheduled transmissions
are stepping on each other before the prior one
has finished.

Try spacing out your EVENT TIMES and see if
that helps. I'm not sure if that is the problem but
I would be interested to know how you fare.

73

--- Mike Pompey, AE7XB
    Port Orchard, Washington state

On 26 Nov 2017 at 21:54, W. T. Jones wrote:

>
> The usual info:
> Fldigi 4.0.12
> Flamp 2.2.03
> Ubuntu 16.04 LTS up to date with patches.
>
> I use Flamp to send a Sunday Night Bulletin to our County's ARES membership. The bulletin is
> in HTML format. Last January I decided to dive into the Flamp Scripts so that I didn't have to sit
> and watch the computer while it sent the bulletins. It has been working rather well until 2 months
> ago. When the time happens to kick off the Flamp at 0200Z Flamp segment faults. The worst
> part of it is that it is not happening consistently. 3 weeks ago it worked. The past 2 weeks
> including tonight it faulted. I have been trying to figure it out for 2 months without much success.
>
> Here is a sample of the segment faults:
> Sep 24 21:15:00 secaprs kernel: [ 2694.155293] flamp[3038]: segfault at 8 ip 00007fe3fd20d36e
> sp 00007ffc386a0920 error 4 in libstdc++.so.6.0.21[7fe3fd0ee000+172000]
> Oct  1 21:15:00 secaprs kernel: [  991.653993] flamp[2524]: segfault at 8 ip 00007f51f06be36e
> sp 00007fff0b6cab40 error 4 in libstdc++.so.6.0.21[7f51f059f000+172000]
> Oct  1 21:15:00 secaprs ntpd[1191]: 204.2.134.162 local addr 192.168.60.50 -> <null>
> Oct 15 21:15:00 secaprs kernel: [48086.239836] flamp[8674]: segfault at 8 ip 00007faea86e636e
> sp 00007ffcd8dd83b0 error 4 in libstdc++.so.6.0.21[7faea85c7000+172000]
> Oct 15 21:15:10 secaprs kernel: [48096.828457] perf interrupt took too long (5003 > 5000),
> lowering kernel.perf_event_max_sample_rate to 25000
> Oct 21 14:37:00 secaprs kernel: [ 6854.113233] flamp[4324]: segfault at 8 ip 00007f03736da36e
> sp 00007ffc7a8f74b0 error 4 in libstdc++.so.6.0.21[7f03735bb000+172000]
> Oct 21 14:39:00 secaprs kernel: [ 6974.574189] flamp[4595]: segfault at 8 ip 00007f20a60e336e
> sp 00007ffcde5d2a40 error 4 in libstdc++.so.6.0.21[7f20a5fc4000+172000]
> Nov 26 21:00:00 secaprs kernel: [ 9330.602498] flamp[3645]: segfault at 8 ip 00007f77ca99736e
> sp 00007ffe78c08390 error 4 in libstdc++.so.6.0.21[7f77ca878000+172000]
> Nov 26 21:02:00 secaprs kernel: [ 9450.500065] flamp[3729]: segfault at 8 ip 00007f01b64d436e
> sp 00007ffffb687460 error 4 in libstdc++.so.6.0.21[7f01b63b5000+172000]
>
> Attached is the script and the bulletin for tonight. Any ideas would be helpful as to what I am
> doing wrong.
>
>
>
>
> Regards,
>
> WT
> Real heroes do not wear capes. They wear dog tags, turnout gear, and badges!
>
>



Electronics usually stop working once the magic smoke is released.






dead psk carrier

Dave
 

Someone has been transmitting an unmodulated PSK signal on 14071.725 for past 15 minutes.  Hopefully that person reads this email.

73, David, W1HKJ

Re: Flamp Segment Fault using Scrip

Robert Stiles <kk5vd@...>
 

WT, So far I have not been able to duplicate the crash in this machine (MacOSX) going to need a full backtrace using gdb as indicated by Dave. Just for testing purposes try increasing the hamcast interval times (all four) by one minute. See if the issue continues.  

Re: Flamp Segment Fault using Script

Robert Stiles <kk5vd@...>
 

WT, Sorry I ment to say increase the time gap between each of the internal times by one minute.

Robert, KK5VD


Groups.io Links:

You receive all messages sent to this group.

View/Reply Online (#14802) | Reply To Group | Reply To Sender | Mute This Topic | New Topic



Terms Of Service
Unsubscribe From This Group

_._,_._,_

Re: Flamp Segment Fault using Scrip

W. T. Jones
 

GE Robert,

OK, on the increase in intervals.

However, so far testing has not resulted in a segfault. "Never happens when you want it to. sigh!"

I have it set to run at 0200Z tonight under the same conditions that resulted in the failure last Sunday.

I will get any information that I get out to you and Dave as soon as I get it.

Thank you for the help.

Regards,

WT
Real heroes do not wear capes. They wear dog tags, turnout gear, and badges!

On Wed, Nov 29, 2017 at 5:51 PM, Robert Stiles via Groups.Io <kk5vd@...> wrote:
WT, So far I have not been able to duplicate the crash in this machine (MacOSX) going to need a full backtrace using gdb as indicated by Dave. Just for testing purposes try increasing the hamcast interval times (all four) by one minute. See if the issue continues.  


SourceForge Project of the Month

Dave
 

-------- Forwarded Message --------
Subject: Re: SourceForge Project of the Month
Date: Fri, 1 Dec 2017 13:28:19 +0800
From: Joan Uy Ang <joan.nadene@...>
To: w1hkj <w1hkj@...>


Hi David,

Just thought you should know that your Project of the Month feature is now live on the SourceForge blog! You can view it here: https://sourceforge.net/blog/december-2017-community-choice-project-month-fldigi/

Best regards,
Joan Nadene
SourceForge Community Coordinator