rt2x00.serialmonkey.com

I'd just installed suse 10.3 on my laptop. Configured the driver for rt2500 en Rutilt. All went wel, no complaints about faults. When I will using Rutilt I get the message :

terminate called after throwing an instance of 'std::logic_error'
what(): basic_string::_S_construct NULL not valid
Aborted

After this message Rutilt aborted. What means this message and how can I repair it so I can use Rutilt.

Thank you for your help

Hello,
I have received many report of this bug, I cannot reproduce it but I'm trying to fix it. It would be helpful if you could recompile and run rutilt with debug enabled :
./configure.sh --debug
make
./rutilt
And post the trace here.

Thanks,
Romain

_________________
RutilT developer

before I post a trace: is there any key in the trace I should anonymize?

Could it be due to a compiler update from SuSE 10.2 --> 10.3?

I don't think so. It happens on other distributions.
I have it on Mandriva too.

I can already say that in debug mode the behavior is different.
RutilT is still crashing with the same error, but this time, before the crash the job is done.

attaching debug trace. In my setup the crash always happens when I want to apply a profile. However, the connection is successful, just Rutilt dies.

second try

Thank you for the trace, the program crashes at the same for place for everybody at least. Now, I'm trying to figure out what is going wrong, and it just doesn't make sense so far .
Your comment is interesting Starcrasher, can you elaborate a bit more please?

_________________
RutilT developer

If I go to the "Profiles" tab, choose a profile and click on "Apply" button then RutilT crash.

If rutilt was compiled without --debug option, the profile seems not applied. (This may need to be verified. The reason can be elsewhere since, in some circumstances, the rt73 driver cannot apply key without bringing down and up the interface)

If rutilt was compiled with --debug option, the profile is applied and even the set_ip.sh script is launched (dhclient is kill/started).

It's only an idea, but it seems that rutilt set the auth mode and encryption and then only kill the existing dhcp client and start a new one (by launching set_ip.sh).
If this is correct, it should kill the existing dhcp client before setting up parameters and then only launch a new dhcp client. It may need to separate the set_ip.sh script in two parts.

Absolutely.

Why is it a problem?

_________________
RutilT developer

Sorry for the late answer.
Well, I imagine changing parameters causes errors with the running dhcp client.
What happens if the current network address obtained by the running dhcp client is valid on the new selected network ? Does it appears connected even it is not ?

I see your point, if a new connection is established and dhcp is used, then it should be no problem because the previous dhcp client will be killed, but if it's not the case, then the old dhclient (or whatever the client) will still be running, and the previously assigned address still used.

_________________
RutilT developer

I have this problem, too.
My sistem is ubuntu Gutsy and rutilt is the distribution (ver. 0.15) compiled for ubuntu.

Program closes when I try to apply a profile or after connected to a network in the window where you can scan for available networks.

Then I have to reload rutilt again and the it works the same.

I will post soon the error message.

Meanwhile, any hints? Thank you

The problem has been solved. I'll try to release a new version as soon as possible. Check the Ubuntu package, maybe the fix has been rolled in.

_________________
RutilT developer

the official 0.15v have this fixed?

No, but I hope to release a new version very soon. I'll post a release candidate this week-end.

_________________
RutilT developer