I do not know if the unaligned access activity in the likes of:
db_test:btree_byteswap_unaligned_access_skbd
is some form of FreeBSD requirement or not. But, for armv7
activity, it results in a bus error (and kyua test failure).
Probaly also true native armv7 operation.
===> lib/libc
with ABSOLUTELY NO WARRANTY
This is free software, and you are welcome to redistribute it
under certain conditions; see the file COPYING for details
JACK compiled with System V SHM support.
loading driver ..
Bus error
(End)
Can somebody help me? Can I help somebody? Am I missing something?
T
Hi, Reference:
> From: "Julian H. Stacey"
> Date: Mon, 14 Oct 2013 08:33:35 +0200
"Julian H. Stacey" wrote:
> Anyone else seeing vi dropping out after a while with "Bus error" & no core ?
>
> Seen on 10.0-ALPHA4 & n
Anyone else seeing vi dropping out after a while with "Bus error" & no core ?
Seen on 10.0-ALPHA4 & now on 10.0-ALPHA5
(after buildkernel installkernel buildworld installworld )
It's not hardware, the laptop is stable & has compiled 594 ports so far,
cd /usr/bin ; ls
On Wed, Oct 02, 2013 at 02:35:57PM +0200, Hans Petter Selasky wrote:
> Maybe you can submit the sane guys a bug-report at:
>
> http://www.sane-project.org/sane-backends.html
>
> --HPS
yep I'll do that
--
John
___
freebsd-current@freebsd.org mailing l
On 10/02/13 14:31, John wrote:
Hi,
One for the archives. I'm not sure if your patch had anything to do with it
but I finally got it working by commenting out everything in
/usr/local/etc/sane.d/dll.conf and just uncommenting the one I wanted.
It seems the scanner was being mis-identified
Thank
Hi,
One for the archives. I'm not sure if your patch had anything to do with it
but I finally got it working by commenting out everything in
/usr/local/etc/sane.d/dll.conf and just uncommenting the one I wanted.
It seems the scanner was being mis-identified
Thanks for your help,
--
John
__
ce2808 /dev/pass0
B
C
A 0x802ce3208 /dev/pass1
B
C
A 0x802ce3c08 /dev/pass2
B
C
A 0x802ce4608 /dev/pass3
B
C
A 0x802ce5008 /dev/pass4
B
C
D
E
F
G
Bus error: 10 (core dumped)
Here is the gdb output:
(gdb) bt
#0 0x0008063c1915 in scsi_inquiry () from
/usr/local/lib/sane/libsane-microtek2.so.1
ppens?
--HPS
Sure! Thanks for looking at the problem.
Program received signal SIGBUS, Bus error.
[Switching to Thread 802c07400 (LWP 101021/scanimage)]
0x0008063c1829 in scsi_inquiry ()
from /usr/local/lib/sane/libsane-microtek2.so.1
(gdb) bt
#0 0x0008063c1829 in scsi_inquiry ()
On Tue, Oct 01, 2013 at 02:41:22PM +0200, Hans Petter Selasky wrote:
>
> Hi,
>
> Could you enter "bt" in GDB and show the output when this crash happens?
>
> --HPS
Sure! Thanks for looking at the problem.
Program received signal SIGBUS, Bus error.
[Switching to
en this crash happens?
> >
> > --HPS
>
> Sure! Thanks for looking at the problem.
>
> Program received signal SIGBUS, Bus error.
> [Switching to Thread 802c07400 (LWP 101021/scanimage)]
> 0x0008063c1829 in scsi_inquiry ()
>from /usr/local/lib/sane/libsane-micr
On 10/01/13 14:22, John wrote:
On Sat, Sep 28, 2013 at 02:05:42AM +0300, Artyom Mirgorodskiy wrote:
I just update to current and get bus error when I try to run gphoto2:
Hi,
This might be related - I get SIGBUS when running scanimage (Canon LIDE 110
scanner).
I installed sane backends and
On Sat, Sep 28, 2013 at 02:05:42AM +0300, Artyom Mirgorodskiy wrote:
> I just update to current and get bus error when I try to run gphoto2:
>
> Starting program: /usr/local/bin/gphoto2 --shell
> (no debugging symbols found)...(no debugging symbols found)...(no debugging
> symbol
On 10/01/13 14:10, Artyom Mirgorodskiy wrote:
Thank you. Work fine for me
FYI: Here is the link to the ticket which you can request to get
committed to libgphoto:
https://sourceforge.net/p/gphoto/patches/153/
--HPS
___
freebsd-current@freebsd.org
On 10/01/13 13:11, Artyom Mirgorodskiy wrote:
I removed old libraries:
ls /usr/lib/libusb*
/usr/lib/libusb.a/usr/lib/libusb_p.a /usr/lib/libusbhid.so.4
/usr/lib/libusb.so@ /usr/lib/libusbhid.a /usr/lib/libusbhid_p.a
/usr/lib/libusb.so.3 /usr/lib/libusbhid.so@
and reins
Thank you. Work fine for me
On Tuesday 01 October 2013 13:45:21 Hans Petter Selasky wrote:
> On 10/01/13 13:11, Artyom Mirgorodskiy wrote:
> > I removed old libraries:
> >
> > ls /usr/lib/libusb*
> > /usr/lib/libusb.a/usr/lib/libusb_p.a /usr/lib/libusbhid.so.4
> > /usr/lib/libusb.so@
On 10/01/13 12:24, Artyom Mirgorodskiy wrote:
ls /usr/lib/libusb*
/usr/lib/libusb.a/usr/lib/libusb.so.3 /usr/lib/libusbhid.so@
/usr/lib/libusb.so@ /usr/lib/libusb_p.a /usr/lib/libusbhid.so.4
/usr/lib/libusb.so.2 /usr/lib/libusbhid.a /usr/lib/libusbhid_p.a
Hi,
I se
Can you run the commands listed below?
--HPS
On 10/01/13 12:22, Artyom Mirgorodskiy wrote:
I'm use current
On Tuesday 01 October 2013 11:32:39 Hans Petter Selasky wrote:
Hi,
I cannot reproduce this issue.
gphoto --shell
works fine on 9-stable using PTP protocol.
gphoto2-2.4.14 Comman
Hi,
I cannot reproduce this issue.
gphoto --shell
works fine on 9-stable using PTP protocol.
gphoto2-2.4.14 Command-line frontend to libgphoto2
libgphoto2-2.4.14_3 Universal digital camera control library
Can you provide more information about your system?
uname -a
ls /usr/lib/libusb*
debugging symbols found)...(no debugging
symbols found)...[New LWP 100223]
[New Thread 802806400 (LWP 100223/gphoto2)]
Program received signal SIGBUS, Bus error.
[Switching to Thread 802806400 (LWP 100223/g
uname -a
FreeBSD notebook.alkar.net 10.0-ALPHA3 FreeBSD 10.0-ALPHA3 #10 r255906: Fri Sep
27 14:54:54 EEST 2013 m...@notebook.alkar.net:/usr/obj/usr/src/sys/Work
amd64
ls /usr/lib/libusb*
/usr/lib/libusb.a/usr/lib/libusb.so.3 /usr/lib/libusbhid.so@
/usr/lib/libusb.so@ /usr/l
I'm use current
On Tuesday 01 October 2013 11:32:39 Hans Petter Selasky wrote:
> Hi,
>
> I cannot reproduce this issue.
>
> gphoto --shell
>
> works fine on 9-stable using PTP protocol.
>
> gphoto2-2.4.14 Command-line frontend to libgphoto2
> libgphoto2-2.4.14_3 Universal digital camera c
; >
> > Sent: Saturday 28th September 2013 19:45
> > To: Hans Petter Selasky > <mailto:hans.petter.sela...@bitfrost.no> >
> > Cc: freebsd-current@freebsd.org <mailto:freebsd-current@freebsd.org>
> > Subject: Re: gphoto2 bus error
> >
> >
ptember 2013 19:45
> To: Hans Petter Selasky <mailto:hans.petter.sela...@bitfrost.no> >
> Cc: freebsd-current@freebsd.org <mailto:freebsd-current@freebsd.org>
> Subject: Re: gphoto2 bus error
>
>
>
> I try to build with gcc 4.6 - the same result :(
>
&g
orodskiy > > <mailto:artyom.mirgorod...@gmail.com> >
> > > Sent: Saturday 28th September 2013 1:05
> > > To: freebsd-current@freebsd.org <mailto:freebsd-current@freebsd.org>
> > > Subject: gphoto2 bus error
> > >
> > > I just upda
o a newer gphoto2 version recently?
>
> --HPS
>
> -Original message-
> > From:Artyom Mirgorodskiy > <mailto:artyom.mirgorod...@gmail.com> >
> > Sent: Saturday 28th September 2013 1:05
> > To: freebsd-current@freebsd.org <mailto:freebsd-curren
I just update to current and get bus error when I try to run gphoto2:
Starting program: /usr/local/bin/gphoto2 --shell
(no debugging symbols found)...(no debugging symbols found)...(no debugging
symbols found)...[New LWP 100144]
[New Thread 802806400 (LWP 100144/gphoto2
On Mon, 4 Apr 2011 09:57:13 +0400
Yuri Pankov wrote:
> http://lists.freebsd.org/pipermail/freebsd-ports/2011-March/066146.html
>
> The workaround is `ln -sf j /etc/malloc.conf`.
Thanks a lot. It solved the issue. :-)
Sincerely,
Gour
--
“In the material world, conceptions of good and bad are
_INFO=/tmp/gpg-2HgBHJ/S.gpg-agent:80589:1;
> export GPG_AGENT_INFO;
> [1]80588 bus error gpg-agent --verbose --debug guru --daemon
>
> In the log file there are messages like:
>
> Apr 3 18:34:01 atmarama kernel: pid 48278 (gpg-agent), uid 1001:
> exited on signal 10
>
>
ebug flags: command cache assuan
gpg-agent[80588]: listening on socket `/tmp/gpg-2HgBHJ/S.gpg-agent'
gpg-agent[80589]: gpg-agent (GnuPG) 2.0.17 started
GPG_AGENT_INFO=/tmp/gpg-2HgBHJ/S.gpg-agent:80589:1;
export GPG_AGENT_INFO;
[1]80588 bus error gpg-agent --verbose --debug guru --daemon
Hi Garrett,
On Mon, 31 May 2010 21:36:23 -0700
Garrett Cooper wrote:
> Ok... there appear to be some interesting bits here, but I'm
> curious... when was the last time that you did a build with clang, and
> did you properly clean out /usr/obj, etc since your last compile?
I don't think that I e
On Mon, May 31, 2010 at 9:28 PM, Andrew Reilly wrote:
> On Mon, 31 May 2010 21:17:41 -0700
> Garrett Cooper wrote:
>
>> What _is_ your make.conf though?
>
> Just this:
>
> #CC=clang
> CFLAGS+=-g
> CXXFLAGS+=-g
> KERNCONF=DUNCAN
>
> NO_LPR=YES
> NO_SENDMAIL=YES
> WITH_GTK2=yes
> WITH_CUPS=yes
> WI
On Mon, 31 May 2010 21:17:41 -0700
Garrett Cooper wrote:
> What _is_ your make.conf though?
Just this:
#CC=clang
CFLAGS+=-g
CXXFLAGS+=-g
KERNCONF=DUNCAN
NO_LPR=YES
NO_SENDMAIL=YES
WITH_GTK2=yes
WITH_CUPS=yes
WITH_GECKO=libxul
#WITH_DEBUG=yes
A4=yes
QT4_OPTIONS=CUPS NAS QGTKSTYLE
PORTSDIR=/nb/
On Mon, May 31, 2010 at 9:06 PM, Andrew Reilly wrote:
> On Mon, 31 May 2010 16:30:04 +0300
> Andriy Gapon wrote:
>
>> Have you been playing with clang or other alternative compilers?
>
> I have them all installed, but none are used by the build
> process. My make.conf is relatively clean.
What
On Mon, 31 May 2010 16:30:04 +0300
Andriy Gapon wrote:
> Have you been playing with clang or other alternative compilers?
I have them all installed, but none are used by the build
process. My make.conf is relatively clean.
> If not, then I think that it's your hardware.
I did too at first. C
mon/avl/avl.c:128:
> internal compiler error: Bus error: 10 Please submit a full bug report, with
> preprocessed source if appropriate. See http://gcc.gnu.org/bugs.html> for
> instructions. *** Error code 1
>
> Stop in /nb/src/cddl/usr.bin/sgsmsg.
>
> Also, if I run b
dodgy: everything else
seems to be working properly. cc itself seems to work OK when
compiling my own code, too. But make buildworld -->
/nb/src/cddl/usr.bin/sgsmsg/../../../sys/cddl/contrib/opensolaris/common/avl/avl.c:128:
internal compiler error: Bus error: 10
Please submit a full bug repo
> # set CFLAGS="$CFLAGS -g"
> # make
Arg! Please use
# make CFLAGS='-O -g'
instead.
signature.asc
Description: Digital signature
Hi,
> Hi today, cvsup'ed my source and build world ...
> and now get an so called
>
> Bus error
>
> while i want to su, anyone know about it (or fixed it)
I think the best is to build debugging version of su:
# cd /usr/src/usr.bin/su
# make clean
# make depend
#
On Sat, 15 Nov 2003, Philipp Westphal wrote:
> Hi today, cvsup'ed my source and build world ...
> and now get an so called
>
> Bus error
>
> while i want to su, anyone know about it (or fixed it)
1) Adjust your system clock so that it's set to something reasonable.
2
Hi today, cvsup'ed my source and build world ...
and now get an so called
Bus error
while i want to su, anyone know about it (or fixed it)
tnx
wasa
there is a fine
FreeBSD 5.1 Release Enlightenment BUS ERROR
all actions performed as root
installed 5.1 beta 2
installed bash from ports
then cvsuped to 5.1 release
then from ports installed xfree86, enlightenment, eterm, all with out problems. While
compiling mozilla from one login, i logged in again on
Hi,
I have been trying to use Jetty with RC3 and not having any
luck.
Today I pinned it down to a problem with trying to convert
a
SocketListener to a String! The following short program
crashes
in exactly the same way as Jetty... Any ideas how to fix
this?
Thank you,
-Will
===sni
On Thu, Jul 04, 2002 at 09:20:38AM -0500, Richard Seaman, Jr. wrote:
> On Tue, Jul 02, 2002 at 06:04:36PM -0700, Joel M. Baldwin wrote:
> >
> >
> > Something has messed up natd. If I don't have the
> > punch_fw option in the /etc/natd.conf file it eventuially
Here, if I "enable nat yes" in /etc/ppp/ppp.conf and forget to turn
net.inet.ip.forwarding on, ppp will core dump in several minutes.
David Xu
--- "Richard Seaman, Jr." <[EMAIL PROTECTED]> wrote:
> On Mon, Jul 08, 2002 at 07:08:58AM -0700, David Xu wrote:
> > you have turned on "nat enable yes"
Hello,
> > Yes, I've seen the same thing on a pre-KSE kernel. The error
> > occurs in PunchFWHole in alias_db.c in libalias. Reverting
> > the following commit seems to fix it (I haven't had a chance
> > to investigate further):
<...>
> > sys/netinet ip_fw.h
Reverting only this
ok, there is a good PR on this one with a reasonable fix:
http://www.freebsd.org/cgi/query-pr.cgi?pr=40331
I am going to commit this and a few other fixes tonight.
cheers
luigi
On Mon, Jul 08, 2002 at 11:28:15AM -0500, Richard Seaman, Jr. wrote:
> On Mon, Jul 08, 2002 a
On Mon, Jul 08, 2002 at 09:07:39AM -0700, Joel M. Baldwin wrote:
>
> I'll have to ditto that.
>
> no ppp, just natd, and sysctl stuff is set as listed below.
>
> Without the punch-fw directive in /etc/natd.conf, natd will core dump.
> I just verified that without the directive it core dumps. T
I'll have to ditto that.
no ppp, just natd, and sysctl stuff is set as listed below.
Without the punch-fw directive in /etc/natd.conf, natd will core dump.
I just verified that without the directive it core dumps. The problem
still exits. It isn't an instant dump, it runs for a while.
--On M
--On Monday, July 08, 2002 9:18 AM -0500 "Richard Seaman, Jr."
<[EMAIL PROTECTED]> wrote:
> On Mon, Jul 08, 2002 at 07:08:58AM -0700, David Xu wrote:
>> you have turned on "nat enable yes" in ppp.conf,
>> and but you havn't turned ip_foward on in sysctl,
>> so core dumped.
>>
>> David Xu
>
> Wel
On Mon, Jul 08, 2002 at 07:08:58AM -0700, David Xu wrote:
> you have turned on "nat enable yes" in ppp.conf,
> and but you havn't turned ip_foward on in sysctl,
> so core dumped.
>
> David Xu
Well, I'm not running ppp, and never indicated I was. I'm running
natd.
# sysctl -a | grep forward
n
"Joel M. Baldwin" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>
Sent: Monday, July 08, 2002 7:12 PM
Subject: Re: natd core dumping with bus error
> On Mon, Jul 08, 2002 at 02:26:10AM -0700, Luigi Rizzo wrote:
> > Could you clarify the problem ?
> > I believe the
ntered the problem.
I created a debug version of natd (but not libalias) and
saw that the bus error was in PunchFWHole. Since I didn't have
a debug version of libalias, I can't tell you what line.
Perhaps PunchFWHole is being called when its not supposed to be,
with bad values?
--
Rich
e is my original message:
> Something has messed up natd. If I don't have the
> punch_fw option in the /etc/natd.conf file it eventuially
> core dumps with a bus error. I think this started JUST
> BEFORE the KSE commit.
>
>
>
> /etc/natd.conf: ( note that this works. com
win wrote:
> >
> >
> > Something has messed up natd. If I don't have the
> > punch_fw option in the /etc/natd.conf file it eventuially
> > core dumps with a bus error. I think this started JUST
> > BEFORE the KSE commit.
>
> Yes, I've seen th
On Thu, Jul 04, 2002 at 09:20:38AM -0500, Richard Seaman, Jr. wrote:
> On Tue, Jul 02, 2002 at 06:04:36PM -0700, Joel M. Baldwin wrote:
> >
> >
> > Something has messed up natd. If I don't have the
> > punch_fw option in the /etc/natd.conf file it eventuially
On Tue, Jul 02, 2002 at 06:04:36PM -0700, Joel M. Baldwin wrote:
>
>
> Something has messed up natd. If I don't have the
> punch_fw option in the /etc/natd.conf file it eventuially
> core dumps with a bus error. I think this started JUST
> BEFORE the KSE commit.
Yes, I
Something has messed up natd. If I don't have the
punch_fw option in the /etc/natd.conf file it eventuially
core dumps with a bus error. I think this started JUST
BEFORE the KSE commit.
/etc/natd.conf: ( note that this works. comment out the
punch_fw option a
In the last episode (Mar 30), Kris Kennaway said:
> On Sat, Mar 30, 2002 at 06:40:52PM +0100, Miguel Mendez wrote:
> > On Sat, Mar 30, 2002 at 02:17:45PM +0100, Miguel Mendez wrote:
> >
> > Just for the record, and to make things more fun, the program works when
> > linked with efence. Could this
On Sat, Mar 30, 2002 at 10:58:58PM +0100, Miguel Mendez wrote:
> Why this problem doesn't show on -STABLE is still beyond my
> comprehension, default malloc behaviour maybe?
-stable has different default settings for malloc.conf, that's
probably why it didn't show up. the -current settings are
On Sat, Mar 30, 2002 at 01:31:09PM -0800, Kris Kennaway wrote:
Hi Terry and Kris,
> Sounds like it could be the malloc.conf defaults on -current exposing
> a bug in the program code.
Yes, there was a bug in my code, it just didn't show up on -STABLE.
Apparently, when one uses efence, allocated
On Sat, Mar 30, 2002 at 06:40:52PM +0100, Miguel Mendez wrote:
> On Sat, Mar 30, 2002 at 02:17:45PM +0100, Miguel Mendez wrote:
>
> Just for the record, and to make things more fun, the program works when
> linked with efence. Could this narrow the problem to libc? Any ideas?
Sounds like it coul
Miguel Mendez wrote:
>
> On Sat, Mar 30, 2002 at 02:17:45PM +0100, Miguel Mendez wrote:
>
> Just for the record, and to make things more fun, the program works when
> linked with efence. Could this narrow the problem to libc? Any ideas?
Sounds like a change in the libdialig stuff is biting you.
On Sat, Mar 30, 2002 at 02:17:45PM +0100, Miguel Mendez wrote:
Just for the record, and to make things more fun, the program works when
linked with efence. Could this narrow the problem to libc? Any ideas?
Cheers,
--
Miguel Mendez - [EMAIL PROTECTED]
GPG Public Key :: http://ene
run it on -CURRENT, it works as well, but, if I compile that code on
-CURRENT, the program dies with a Bus Error the moment I enter the Knobs
menu. I've seen this problem both with the 11th of March snapshot and
with a world I built yesterday, cvsupped at 1500 UTC. The current box
specs are thes
configured as "i386-unknown-freebsd"...
(no debugging symbols found)...
Core was generated by `gs'.
Program terminated with signal 10, Bus error.
Reading symbols from /usr/local/lib/libpng.so.5...
(no debugging symbols found)...done.
Reading symbols from /usr/lib/libz.so.2...(no debug
> > Has anyone else noticed savecore core dumping on a bus error? I think it
> > started on my yesterday's make world. Redid the make world today with the
> > latest sources and it's still doing it. Leaves a nice savecore.core in /.
>
> Try the enclosed patc
> Has anyone else noticed savecore core dumping on a bus error? I think it
> started on my yesterday's make world. Redid the make world today with the
> latest sources and it's still doing it. Leaves a nice savecore.core in /.
Try the enclosed patch.
- Tor Egge
I
Blaz Zupan wrote:
>
> Has anyone else noticed savecore core dumping on a bus error? I think it
> started on my yesterday's make world. Redid the make world today with the
> latest sources and it's still doing it. Leaves a nice savecore.core in /.
A while ago, passwd was
Has anyone else noticed savecore core dumping on a bus error? I think it
started on my yesterday's make world. Redid the make world today with the
latest sources and it's still doing it. Leaves a nice savecore.core in /.
Blaz Zupan, Medinet d.o.o, Linhartova 21, 2000 Maribor, Slove
Thimble Smith wrote:
> Hello. I have a reproducable problem which gdb says is ending up at
> 0x2818d862 in isatty() from /usr/lib/libc.so.3. A full back trace is
> below. If this is a problem in FreeBSD, I'm very glad to do any
> experiments that might be helpful. If it's a problem somewhere e
im' 'ign0rant')
(no debugging symbols found)...
Program received signal SIGBUS, Bus error.
0x2818d862 in isatty () from /usr/lib/libc.so.3
(gdb) back
#0 0x2818d862 in isatty () from /usr/lib/libc.so.3
#1 0x2818db22 in isatty () from /usr/lib/libc.so.3
#2 0x2818e1de in malloc () from /
72 matches
Mail list logo
