kopia lustrzana https://gitlab.com/sane-project/website
77 wiersze
3.4 KiB
HTML
77 wiersze
3.4 KiB
HTML
<!-- received="Fri Oct 10 09:34:58 1997 MST" -->
|
||
<!-- sent="Fri, 10 Oct 1997 18:33:32 +0200 (MET DST)" -->
|
||
<!-- name="Peter Daum" -->
|
||
<!-- email="gator@cs.tu-berlin.de" -->
|
||
<!-- subject="Re: umax: xscanimage does not run run as gimp plugin" -->
|
||
<!-- id="" -->
|
||
<!-- inreplyto="Pine.LNX.3.96.971009143034.8415A-100000@swamp.bayern.net" -->
|
||
<title>sane-devel: Re: umax: xscanimage does not run run as gimp plugin</title>
|
||
<h1>Re: umax: xscanimage does not run run as gimp plugin</h1>
|
||
<b>Peter Daum</b> (<a href="mailto:gator@cs.tu-berlin.de"><i>gator@cs.tu-berlin.de</i></a>)<br>
|
||
<i>Fri, 10 Oct 1997 18:33:32 +0200 (MET DST)</i>
|
||
<p>
|
||
<ul>
|
||
<li> <b>Messages sorted by:</b> <a href="date.html#53">[ date ]</a><a href="index.html#53">[ thread ]</a><a href="subject.html#53">[ subject ]</a><a href="author.html#53">[ author ]</a>
|
||
<!-- next="start" -->
|
||
<li> <b>Next message:</b> <a href="0054.html">Jeff Freedman: "Re: Java API"</a>
|
||
<li> <b>Previous message:</b> <a href="0052.html">Oliver.Rauch@Wolfsburg.DE: "Re: segfault with sane-umax"</a>
|
||
<!-- nextthread="start" -->
|
||
<!-- reply="end" -->
|
||
</ul>
|
||
<!-- body="start" -->
|
||
On Thu, 9 Oct 1997, Peter Daum wrote:<br>
|
||
...<br>
|
||
<i>> I don't know enough about sane, gtk and gimp to make any sense of this.</i><br>
|
||
...<br>
|
||
<p>
|
||
Well, I still don't know much more ;-)<br>
|
||
However, I did try to find out what is actually going on when<br>
|
||
xscanimage crashes on startup:<br>
|
||
<p>
|
||
It looks like there is a segfault occuring at the same position,<br>
|
||
where otherwise the "** WARNING **: file gtkwidget.c: line 2813<br>
|
||
..." warnings. Here's a backtrace:<br>
|
||
<p>
|
||
Starting program: xscanimage umax:/dev/scanner<br>
|
||
Program received signal SIGSEGV, Segmentation fault.<br>
|
||
0x400a03fe in gtk_real_widget_queue_draw (widget=0x80a41a0) at gtkwidget.c:2813<br>
|
||
(gdb) bt<br>
|
||
#0 0x400a03fe in gtk_real_widget_queue_draw (widget=0x80a41a0) at gtkwidget.c:2813<br>
|
||
#1 0x40055e91 in gtk_idle_invoke_function (idlef=0x80a3388) at gtkmain.c:903<br>
|
||
#2 0x40055f49 in gtk_handle_idle () at gtkmain.c:934<br>
|
||
#3 0x40055134 in gtk_main_iteration () at gtkmain.c:377<br>
|
||
#4 0x40054d50 in gtk_main () at gtkmain.c:377<br>
|
||
#5 0x804e962 in interface (argc=2, argv=0xbffff254) at xscanimage.c:1652<br>
|
||
#6 0x804e9d6 in main (argc=2, argv=0xbffff254) at xscanimage.c:1681<br>
|
||
#7 0x804c30e in ___crt_dummy__ ()<br>
|
||
<p>
|
||
These crashes don't occur every time the program is started and<br>
|
||
seem to occur more often, when the device is given on the command<br>
|
||
line than when the device is selected in the dialog. Could there<br>
|
||
be some sort of race condition somewhere?<br>
|
||
<p>
|
||
Maybe, somebody else knows more ...<br>
|
||
<p>
|
||
Peter<br>
|
||
<pre>
|
||
--
|
||
| Peter Daum (<a href="mailto:gator@cs.tu-berlin.de">gator@cs.tu-berlin.de</a>) __o (+49 30)
|
||
| <a href="http://www.cs.tu-berlin.de/~gator">http://www.cs.tu-berlin.de/~gator</a> _'\<_ 691 46 35
|
||
| pgp messages welcome! _(_)/(_) ___________
|
||
<p>
|
||
<p>
|
||
<pre>
|
||
--
|
||
Source code, list archive, and docs: <a href="http://www.mostang.com/sane/">http://www.mostang.com/sane/</a>
|
||
To unsubscribe: echo unsubscribe sane-devel | mail <a href="mailto:majordomo@mostang.com">majordomo@mostang.com</a>
|
||
</pre>
|
||
<!-- body="end" -->
|
||
<p>
|
||
<ul>
|
||
<!-- next="start" -->
|
||
<li> <b>Next message:</b> <a href="0054.html">Jeff Freedman: "Re: Java API"</a>
|
||
<li> <b>Previous message:</b> <a href="0052.html">Oliver.Rauch@Wolfsburg.DE: "Re: segfault with sane-umax"</a>
|
||
<!-- nextthread="start" -->
|
||
<!-- reply="end" -->
|
||
</ul>
|