<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
<br>
<blockquote cite="mid:20090316131657.118072cp6iebuq68@mail.de-korte.org"
type="cite">
<pre wrap="">Citeren Attila Csontos <a class="moz-txt-link-rfc2396E" href="mailto:attila.csontos@r-sys.sk"><attila.csontos@r-sys.sk></a>:
</pre>
<blockquote type="cite">
<pre wrap=""> Hi Kjell and Arnaud,
</pre>
</blockquote>
<pre wrap=""><!---->
</pre>
<blockquote type="cite">
<pre wrap="">I was trying Kjell's command (/path/to/bcmxcp -DD -a pw9130 -u root)
and I have got this output:
</pre>
</blockquote>
<pre wrap=""><!---->
[...]
</pre>
<blockquote type="cite">
<pre wrap="">After that driver finished with Segmentation Fault (core dumped). No
core file in current directory.
</pre>
</blockquote>
<pre wrap=""><!---->
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>
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>
<br>
Attila<br>
</body>
</html>