Re: [Linecontrol-development] segfault problem in linesrv still occurs

[S. F. <sf...@gm...>]

>Oct  7 20:42:15 lfsPentiumRouter linesrv[1996]: Value of segf_indicator: 16

Good... that's what I need. Unfortunately there was bug until now (fixed
in cvs as of Oct 8th 09:47 MET [+0200]).
Could you take the actual cvs version and reproduce the segfault?
The value 16 here is probable (90% or more) wrong...
(jp: you don't have cvs working?... wait, you'll get a copy...)

>Those 2 lines above where 192.168.1.8 gets online twice are related to that
>bug report I issued earlier.
>As we can see, there is no offline() called by the client in the middle.
>Each of those calls would call isdn-up twice and isdn-off once

>dialed ippp0 at Sun Oct  7 21:00:29 WEST 2001
>dialed ippp0 at Sun Oct  7 21:00:31 WEST 2001
>Issued hangup at Sun Oct  7 21:00:40 WEST 2001

These lines, are they coming from isdn4linux? If yes: to check how many
times your script_up got called you have to add a line in the script_up:

echo "script_up called: `date`" >> /var/log/updownstuff.log

Anything else is crap for me and doesn't help. (sorry).

>I don't see much info here but...
>About the segfault, this seems the problem introduceb by my change to get
>multiple ISP, as that
>"safety code" I cuted would mask whatever is the problem here by forcing the
>lines to close...

I'm not going to bother about your changes because I didn't see your code.
So if you report bugs, please use either cvs oder some version I released
(at least: send me the code or a diff...)
When you're talking about code: please notice the file and line you're talking
about... I just can't catch up.

>Somehow I get the feeling that if the newer version have some work around
>this problem, it has been away from the real cause of it and it will get
>away eventually only in the new 3.x version... So maybe lets not bother too
>much about this!

About 3: It will have new bugs and can't be compared to 2.x or earlier. It's
written in C++ and has a completely different concept in it's code. Have a look
at it and you'll see that... ;)
Start it with "linesrv -d" if you wan't to see a list of all keywords, their
defaults and format strings. Config parsing works. Now I'll have a look at
the lcp3 implementation...

>Can this behaviour be introduced by some missing option in my config file ?
>(I'm using the same in 2.1.4 as in 2.1.0)

Send me your config file... maybe you already sent it some weeks / months ago...
but hey, I don't collect config files... ;) I answer the mail and then the whole
thing gets deleted.


The segfault bug: you're not the only one... but I currently don't have any installed
isdncard or even analog modem. So the only way is to simulate the whole thing... that's
not quite easy. But I would be happy to get the following thing:

you're offline, isdn line is closed
# cat /dev/isdninfo > somefile.iinfo &
[1] <pid>
# <dial line, online, hangup, closed >
# kill <pid>
# gz somefile.iinfo
then mail me somefile.iinfo.gz

This would allow me to write a isdninfo emulator (using a pipe) to debug
isdn code of linesrv 3 (and 2.1.x too...)

And if someone of you is using a strange isdn config (multiple cards, tons
of channels, or whathever) please send me the same... ;)

Greetings & thanks for your reports.

Stefan Fuchs