Citeren Attila Csontos <[email protected]>:

  
     Hi Kjell and Arnaud,
    

  
I was trying Kjell's command (/path/to/bcmxcp -DD -a pw9130 -u root)
and I have got this output:
    

[...]

  
After that driver finished with Segmentation Fault (core dumped). No
core file in current directory.
    

If you care to attempt to debug what is going in, it might help to run  
the above command through 'valgrind'. This will allow examining what  
causes the segmentation fault. This could be bcmxcp driver specific or  
(worse) be caused by an error in the main driver core functions.  
Especially in the latter case I would really like to see what is going  
on.

Best regards, Arjen
  
Unfortunatelly , there is no 'valgrind' on Solaris....maybe in next version :-)
But I have started bcmxcp driver in gdb, and I got  this result

Program received signal SIGSEGV, Segmentation fault.
0xfedc58fc in strlen () from /usr/lib/libc.so.1
(gdb) bt
#0  0xfedc58fc in strlen () from /usr/lib/libc.so.1
#1  0xfee1ed96 in _ndoprnt () from /usr/lib/libc.so.1
#2  0xfee21ecb in vsnprintf () from /usr/lib/libc.so.1
#3  0x08058b31 in vupslog ()
#4  0x08058db7 in upsdebugx ()
#5  0x08054aa6 in upsdrv_initinfo ()
#6  0x080569ed in main ()
(gdb)

It happens only when I start driver with -DD (or more 'D'). When I run only with -D, it working normally.

Attila
_______________________________________________
Nut-upsuser mailing list
[email protected]
http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser

Reply via email to