<br><br><div class="gmail_quote">2009/3/16 Attila Csontos <span dir="ltr"><<a href="mailto:attila.csontos@r-sys.sk">attila.csontos@r-sys.sk</a>></span><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div bgcolor="#ffffff" text="#000000"><div class="im">
<br>
<blockquote type="cite">
<pre>Citeren Attila Csontos <a href="mailto:attila.csontos@r-sys.sk" target="_blank"><attila.csontos@r-sys.sk></a>:
</pre>
<blockquote type="cite">
<pre> Hi Kjell and Arnaud,
</pre>
</blockquote>
<pre> </pre>
<blockquote type="cite">
<pre>I was trying Kjell's command (/path/to/bcmxcp -DD -a pw9130 -u root)
and I have got this output:
</pre>
</blockquote>
<pre>[...]
</pre>
<blockquote type="cite">
<pre>After that driver finished with Segmentation Fault (core dumped). No
core file in current directory.
</pre>
</blockquote>
<pre>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
</pre>
</blockquote></div>
Unfortunatelly , there is no 'valgrind' on Solaris....maybe in next
version :-)<br>
But I have started bcmxcp driver in gdb, and I got this result<br>
<br>
Program received signal SIGSEGV, Segmentation fault.<br>
0xfedc58fc in strlen () from /usr/lib/libc.so.1<br>
(gdb) bt<br>
#0 0xfedc58fc in strlen () from /usr/lib/libc.so.1<br>
#1 0xfee1ed96 in _ndoprnt () from /usr/lib/libc.so.1<br>
#2 0xfee21ecb in vsnprintf () from /usr/lib/libc.so.1<br>
#3 0x08058b31 in vupslog ()<br>
#4 0x08058db7 in upsdebugx ()<br>
#5 0x08054aa6 in upsdrv_initinfo ()<br>
#6 0x080569ed in main ()<br>
(gdb)<br>
<br>
It happens only when I start driver with -DD (or more 'D'). When I run
only with -D, it working normally.<br>
</div></blockquote><div><br>all the debug outputs there are at level 2. so nothing but "normal".<br>from your feedback, my guess is that it crashes at the Config_block (line 1108)<br>the gdb trace just before the crash should confirm this (last one should be: "Length of alarm map...")<br>
</div></div>Kjell will (or not) confirm since I'm not an XCP expert...<br><br>cheers,<br>Arnaud<br>-- <br>Linux / Unix Expert R&D - Eaton - <a href="http://www.eaton.com/mgeops">http://www.eaton.com/mgeops</a><br>
Network UPS Tools (NUT) Project Leader - <a href="http://www.networkupstools.org/">http://www.networkupstools.org/</a><br>Debian Developer - <a href="http://people.debian.org/~aquette/">http://people.debian.org/~aquette/</a><br>
Free Software Developer - <a href="http://arnaud.quette.free.fr/">http://arnaud.quette.free.fr/</a><br><br>