aarch64/armv7 via lib32 and via chroot: db_test:btree_byteswap_unaligned_access_skbd gets bus error
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/db/db_test:btree_byteswap_unaligned_access_skbd Result: failed: atf-check failed; see the output of the test for details Start time: 2023-08-01T09:07:38.975390Z End time: 2023-08-01T09:07:39.006220Z Duration: 0.031s Metadata: allowed_architectures is empty allowed_platforms is empty description = btree: small key, big data, byteswap unaligned access has_cleanup = false is_exclusive = false required_configs is empty required_disk_space = 0 required_files is empty required_memory = 0 required_programs is empty required_user is empty timeout = 300 Standard output: Executing command [ /usr/obj/DESTDIRs/main-CA7-chroot/usr/tests/lib/libc/db/h_db -o out -i psize=512,lorder=1234 btree in ] Executing command [ /usr/obj/DESTDIRs/main-CA7-chroot/usr/tests/lib/libc/db/h_db -o out -i psize=512,lorder=4321 btree in ] Standard error: Fail: program did not exit cleanly stdout: stderr: Files left in work directory after failure: h_db.core, in, out For reference: Reading symbols from /usr/obj/DESTDIRs/main-CA7-chroot/usr/tests/lib/libc/db/h_db... (No debugging symbols found in /usr/obj/DESTDIRs/main-CA7-chroot/usr/tests/lib/libc/db/h_db) [New LWP 102818] Core was generated by `/usr/obj/DESTDIRs/main-CA7-chroot/usr/tests/lib/libc/db/h_db -o out -i psize=512'. Program terminated with signal SIGBUS, Bus error. Invalid address alignment. #0 __bt_pgout (t=, pg=, pp=0x4060651c) at /usr/main-src/lib/libc/db/btree/bt_conv.c:174 174 P_32_SWAP(p); (gdb) bt #0 __bt_pgout (t=, pg=, pp=0x4060651c) at /usr/main-src/lib/libc/db/btree/bt_conv.c:174 #1 0x401468ac in mpool_write (mp=0x4061, bp=0x40606500) at /usr/main-src/lib/libc/db/mpool/mpool.c:406 #2 mpool_sync (mp=0x4061) at /usr/main-src/lib/libc/db/mpool/mpool.c:329 #3 0x4013d548 in __bt_sync (dbp=, dbp@entry=0x4060b000, flags=) at /usr/main-src/lib/libc/db/btree/bt_close.c:146 #4 0x4013d35c in __bt_close (dbp=0x4060b000) at /usr/main-src/lib/libc/db/btree/bt_close.c:80 #5 0x000221b4 in main () === Mark Millard marklmi at yahoo.com
Jack not working: Bus error
I tried ports and packages. I get the same on both. Tried as normal user and superuser. Same results. Console sample: (Start) /usr/local/bin/jackd -r -doss -r48000 -p1024 -n2 -w16 jackd 0.124.1 Copyright 2001-2009 Paul Davis, Stephane Letz, Jack O'Quinn, Torben Hohn and others. jackd comes 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? Thanks! ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: vi drop outs with Bus error
Hi, Reference: From: Julian H. Stacey j...@berklix.com 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 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 -l nvi* -r-xr-xr-x 1 root wheel 402064 Oct 12 02:42 nvi.4* -r-xr-xr-x 1 root wheel 402432 Oct 12 02:42 nvi.5* file nvi* nvi.4: ELF 64-bit LSB executable, x86-64, version 1 (FreeBSD), dynamically \ linked (uses shared libs), for FreeBSD 10.0 (155), stripped nvi.5: ELF 64-bit LSB executable, x86-64, version 1 (FreeBSD), dynamically \ linked (uses shared libs), for FreeBSD 10.0 (155), stripped I'm no longer seeing drop outs with Bus error, instead, after xterm -sl 1024 -g 80x24 -j -n lapr -e rlogin -D 10beta1host vi freezes within the xterm after I do an X11 mouse resize (maybe that same SIGWINCH was causing Bus Error before, as resize I tend to do a lot without remembering :-) Anyone else see it ? Cheers, Julian -- Julian Stacey, BSD Unix Linux C Sys Eng Consultant, Munich http://berklix.com Interleave replies below like a play script. Indent old text with . Send plain text, not quoted-printable, HTML, base64, or multipart/alternative. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
vi drop outs with Bus error
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 -l nvi* -r-xr-xr-x 1 root wheel 402064 Oct 12 02:42 nvi.4* -r-xr-xr-x 1 root wheel 402432 Oct 12 02:42 nvi.5* file nvi* nvi.4: ELF 64-bit LSB executable, x86-64, version 1 (FreeBSD), dynamically \ linked (uses shared libs), for FreeBSD 10.0 (155), stripped nvi.5: ELF 64-bit LSB executable, x86-64, version 1 (FreeBSD), dynamically \ linked (uses shared libs), for FreeBSD 10.0 (155), stripped Cheers, Julian -- Julian Stacey, BSD Unix Linux C Sys Eng Consultant, Munich http://berklix.com Reply below not above, like a play script. Indent old text with . Send plain text. No quoted-printable, HTML, base64, multipart/alternative. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: gphoto2 bus error
On 10/01/13 15:50, John wrote:
sorry, forgot to change From:, sending again
On Tue, Oct 01, 2013 at 02:45:29PM +0100, John wrote:
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 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 ()
from /usr/local/lib/sane/libsane-microtek2.so.1
#1 0x0008063b384c in attach ()
from /usr/local/lib/sane/libsane-microtek2.so.1
#2 0x0008063b4a69 in attach_one ()
from /usr/local/lib/sane/libsane-microtek2.so.1
#3 0x00080083205b in sanei_scsi_find_devices ()
from /usr/local/lib/libsane.so.1
#4 0x00080082ef1e in sanei_config_attach_matching_devices ()
from /usr/local/lib/libsane.so.1
#5 0x0008063b4993 in sane_microtek2_init ()
from /usr/local/lib/sane/libsane-microtek2.so.1
#6 0x00080083acb4 in init () from /usr/local/lib/libsane.so.1
#7 0x00080083a944 in sane_dll_get_devices ()
from /usr/local/lib/libsane.so.1
#8 0x00402089 in ?? ()
#9 0x00401c41 in ?? ()
#10 0x000800628000 in ?? ()
#11 0x in ?? ()
(gdb)
--
John
Hi,
Can you try to apply the attached patch to:
cd /usr/ports/graphics/sane-backends
make clean extract patch
cd /usr/ports/graphics/sane-backends/work/sane-backends-1.0.23
cat sane-backend-debug.diff | patch -p1
cd /usr/ports/graphics/sane-backends
make all deinstall install
Maybe you can figure out exactly what line is causing the crash by
adding more printf's like shown in the attached patch.
--HPS
diff --git a/backend/microtek2.c b/backend/microtek2.c
index d56e568..1aafa80 100644
--- a/backend/microtek2.c
+++ b/backend/microtek2.c
@@ -4276,6 +4276,8 @@ scsi_send_gamma(Microtek2_Scanner *ms)
/*-- scsi_inquiry() --*/
+#include stdio.h
+
static SANE_Status
scsi_inquiry(Microtek2_Info *mi, char *device)
{
@@ -4286,6 +4288,7 @@ scsi_inquiry(Microtek2_Info *mi, char *device)
size_t size;
int sfd;
+printf(A %p %s\n, mi, device);
DBG(30, scsi_inquiry: mi=%p, device='%s'\n, (void *) mi, device);
@@ -4296,6 +4299,8 @@ scsi_inquiry(Microtek2_Info *mi, char *device)
return status;
}
+printf(B\n);
+
INQ_CMD(cmd);
INQ_SET_ALLOC(cmd, INQ_ALLOC_L);
result = (uint8_t *) alloca(INQ_ALLOC_L);
@@ -4306,6 +4311,8 @@ scsi_inquiry(Microtek2_Info *mi, char *device)
return SANE_STATUS_NO_MEM;
}
+printf(C\n);
+
size = INQ_ALLOC_L;
status = sanei_scsi_cmd(sfd, cmd, sizeof(cmd), result, size);
if ( status != SANE_STATUS_GOOD )
@@ -4315,6 +4322,8 @@ scsi_inquiry(Microtek2_Info *mi, char *device)
return status;
}
+printf(D\n);
+
INQ_GET_INQLEN(inqlen, result);
INQ_SET_ALLOC(cmd, inqlen + INQ_ALLOC_L);
result = alloca(inqlen + INQ_ALLOC_L);
@@ -4328,6 +4337,8 @@ scsi_inquiry(Microtek2_Info *mi, char *device)
if (md_dump = 2 )
dump_area2(cmd, sizeof(cmd), inquiry);
+printf(E\n);
+
status = sanei_scsi_cmd(sfd, cmd, sizeof(cmd), result, size);
if ( status != SANE_STATUS_GOOD )
{
@@ -4337,12 +4348,16 @@ scsi_inquiry(Microtek2_Info *mi, char *device)
}
sanei_scsi_close(sfd);
+printf(F\n);
+
if (md_dump = 2 )
{
dump_area2((uint8_t *) result, size, inquiryresult);
dump_area((uint8_t *) result, size, inquiryresult);
}
+printf(G\n);
+
/* copy results */
INQ_GET_QUAL(mi-device_qualifier, result);
INQ_GET_DEVT(mi-device_type, result);
@@ -4352,6 +4367,7 @@ scsi_inquiry(Microtek2_Info *mi, char *device)
INQ_GET_REV(mi-revision, (char *)result);
INQ_GET_MODELCODE(mi-model_code, result);
+printf(H\n);
return SANE_STATUS_GOOD;
}
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: gphoto2 bus error
On Wed, Oct 02, 2013 at 08:25:30AM +0200, Hans Petter Selasky wrote: Hi, Can you try to apply the attached patch to: cd /usr/ports/graphics/sane-backends make clean extract patch cd /usr/ports/graphics/sane-backends/work/sane-backends-1.0.23 cat sane-backend-debug.diff | patch -p1 cd /usr/ports/graphics/sane-backends make all deinstall install Thanks for the patch! I have applied it now Maybe you can figure out exactly what line is causing the crash by adding more printf's like shown in the attached patch. I think you over-estimate my programming ability! I have soft linked genesys.so as per sane manpages as that's the scanner I have. I don't know why some of the errors are coming up with microtek. $ ls -la /usr/local/lib/sane/libsane.so lrwxr-xr-x 1 root wheel22B 2 Oct 11:59 /usr/local/lib/sane/libsane.so@ - ./libsane-genesys.so.1 sane-find-scanner finds it at found USB scanner (vendor=0x04a9 [Canon], product=0x1909 [CanoScan], chip=GL124) at libusb:/dev/usb:/dev/ugen4.4 OK here is the output from scanimage -L : $ scanimage -L A 0x802ce2808 /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 #1 0x0008063b38dc in attach () from /usr/local/lib/sane/libsane-microtek2.so.1 #2 0x0008063b4af9 in attach_one () from /usr/local/lib/sane/libsane-microtek2.so.1 #3 0x00080083205b in sanei_scsi_find_devices () from /usr/local/lib/libsane.so.1 #4 0x00080082ef1e in sanei_config_attach_matching_devices () from /usr/local/lib/libsane.so.1 #5 0x0008063b4a23 in sane_microtek2_init () from /usr/local/lib/sane/libsane-microtek2.so.1 #6 0x00080083acb4 in init () from /usr/local/lib/libsane.so.1 #7 0x00080083a944 in sane_dll_get_devices () from /usr/local/lib/libsane.so.1 #8 0x00402089 in ?? () #9 0x00401c41 in ?? () #10 0x000800628000 in ?? () #11 0x in ?? () (gdb) Although scanimage -L gives the bus error, the following doesn't: $ scanimage -d genesys -x 100 -y 100 --format=jpg image.jpg I have no idea why microtek2 is in that output. This is a new install and libscan.so is linked to libsane-genesys.so.1 thanks, -- ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: gphoto2 bus error
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 ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: gphoto2 bus error
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 Thanks for your help, Hi, Maybe you can submit the sane guys a bug-report at: http://www.sane-project.org/sane-backends.html --HPS ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: gphoto2 bus error
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 list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: gphoto2 bus error
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 control library Can you provide more information about your system? uname -a ls /usr/lib/libusb* ls /usr/local/libdata/pkgconfig/*usb* Also try to reinstall gphoto: portsnap fetch update cd /usr/ports/graphics/libgphoto2 make all reinstall clean cd /usr/ports/graphics/photo2 make all reinstall clean --HPS -- Artyom Mirgorodskiy ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: gphoto2 bus error
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/lib/libusb_p.a /usr/lib/libusbhid.so.4 /usr/lib/libusb.so.2 /usr/lib/libusbhid.a /usr/lib/libusbhid_p.a ls /usr/local/libdata/pkgconfig/*usb* ls: /usr/local/libdata/pkgconfig/*usb*: No such file or directory On Tuesday 01 October 2013 11:32:39 Hans Petter Selasky wrote: Can you provide more information about your system? uname -a ls /usr/lib/libusb* ls /usr/local/libdata/pkgconfig/*usb* -- Artyom Mirgorodskiy ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: gphoto2 bus error
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 reinstall gphoto2 and libgphoto2 and have the same result :( gdb /usr/local/bin/gphoto2 GNU gdb 6.1.1 [FreeBSD] Copyright 2004 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type show copying to see the conditions. There is absolutely no warranty for GDB. Type show warranty for details. This GDB was configured as amd64-marcel-freebsd...(no debugging symbols found)... (gdb) run --shell Starting program: /usr/local/bin/gphoto2 --shell (no debugging symbols found)...(no 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/gphoto2)] 0x000801553597 in pthread_mutex_destroy () from /lib/libthr.so.3 (gdb) bt #0 0x000801553597 in pthread_mutex_destroy () from /lib/libthr.so.3 #1 0x0008040083cd in libusb_free_device_list () from /usr/lib/libusb.so.3 #2 0x000803801a2a in gp_port_usb_exit (port=value optimized out) at libusb1.c:275 #3 0x000801136763 in gp_port_free (port=0x80286d280) at gphoto2-port.c:124 #4 0x000800ebd6a9 in gp_abilities_list_detect (list=0x802869080, info_list=0x802869050, l=0x8028ec000, context=0x45) at gphoto2-abilities-list.c:488 #5 0x0040673a in ?? () #6 0x0040772f in ?? () #7 0x000800636000 in ?? () #8 0x in ?? () On Tuesday 01 October 2013 12:40:35 Hans Petter Selasky wrote: 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 see you have two versions of libusb installed. You probably need to delete some of the older libraries using the make delete-old-libs and beware you maybe need to rebuild all ports after that! I think gphoto uses libusb.so.2 while you have installed the header file for libusb.so.3. Check that first. gphoto2 --auto-detect and gphoto2 --shell does not crash over here. Let me know if this is still an issue after cleaning out old libraries and files from your system. Thank you! --HPS -- Artyom Mirgorodskiy ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: gphoto2 bus error
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* ls /usr/local/libdata/pkgconfig/*usb* Also try to reinstall gphoto: portsnap fetch update cd /usr/ports/graphics/libgphoto2 make all reinstall clean cd /usr/ports/graphics/photo2 make all reinstall clean --HPS ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: gphoto2 bus error
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 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* ls /usr/local/libdata/pkgconfig/*usb* Also try to reinstall gphoto: portsnap fetch update cd /usr/ports/graphics/libgphoto2 make all reinstall clean cd /usr/ports/graphics/photo2 make all reinstall clean --HPS ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: gphoto2 bus error
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 see you have two versions of libusb installed. You probably need to delete some of the older libraries using the make delete-old-libs and beware you maybe need to rebuild all ports after that! I think gphoto uses libusb.so.2 while you have installed the header file for libusb.so.3. Check that first. gphoto2 --auto-detect and gphoto2 --shell does not crash over here. Let me know if this is still an issue after cleaning out old libraries and files from your system. Thank you! --HPS ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: gphoto2 bus error
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@ /usr/lib/libusbhid.a /usr/lib/libusbhid_p.a /usr/lib/libusb.so.3 /usr/lib/libusbhid.so@ and reinstall gphoto2 and libgphoto2 and have the same result :( Hi, I quickly looked at the gphoto code and see some bugs there. Can you try the attached patch? cd /usr/ports/graphics/libgphoto2 make clean extract patch cd /usr/ports/graphics/libgphoto2/work/libgphoto2-2.4.14 cat libgphoto2.patch | patch -p1 cd /usr/ports/graphics/libgphoto2 make all deinstall install --HPS -- Artyom Mirgorodskiy ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: gphoto2 bus error
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 reinstall gphoto2 and libgphoto2
and have the same result :(
Hi,
I quickly looked at the gphoto code and see some bugs there. Can you try
the attached patch?
cd /usr/ports/graphics/libgphoto2
make clean extract patch
cd /usr/ports/graphics/libgphoto2/work/libgphoto2-2.4.14
cat libgphoto2.patch | patch -p1
cd /usr/ports/graphics/libgphoto2
make all deinstall install
--HPS
diff --git a/libgphoto2_port/libusb1/libusb1.c b/libgphoto2_port/libusb1/libusb1.c
index c6b16aa..74b722f 100644
--- a/libgphoto2_port/libusb1/libusb1.c
+++ b/libgphoto2_port/libusb1/libusb1.c
@@ -84,6 +84,14 @@ static int gp_nrofdevs = 0;
static struct libusb_device_descriptor *gp_descs;
static libusb_device **gp_devs;
+static void
+free_devicelist(void)
+{
+ if (gp_devs != NULL)
+ libusb_free_device_list (gp_devs, 1);
+ gp_devs = NULL;
+}
+
static ssize_t
load_devicelist (libusb_context *ctx) {
time_t xtime;
@@ -91,7 +99,7 @@ load_devicelist (libusb_context *ctx) {
time(xtime);
if (xtime != gp_devslastchecked) {
if (gp_nrofdevs)
- libusb_free_device_list (gp_devs, 1);
+ free_devicelist();
free (gp_descs);
gp_nrofdevs = 0;
gp_devs = NULL;
@@ -267,12 +275,14 @@ static int gp_port_usb_init (GPPort *port)
static int
gp_port_usb_exit (GPPort *port)
{
+ /* devices must be freed before exiting the USB context */
+ free_devicelist();
+
if (port-pl) {
libusb_exit (port-pl-ctx);
free (port-pl);
port-pl = NULL;
}
- if (gp_devs) libusb_free_device_list (gp_devs, 1);
free (gp_descs);
return (GP_OK);
}
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: gphoto2 bus error
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 mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: gphoto2 bus error
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 symbols found)...[New LWP 100144] [New Thread 802806400 (LWP 100144/gphoto2)] Program received signal SIGBUS, Bus error. [Switching to Thread 802806400 (LWP 100144/gphoto2)] 0x000801552597 in pthread_mutex_destroy () from /lib/libthr.so.3 (gdb) bt #0 0x000801552597 in pthread_mutex_destroy () from /lib/libthr.so.3 #1 0x0008040083cd in libusb_free_device_list () from /usr/lib/libusb.so.3 #2 0x000803801a2a in gp_port_usb_exit (port=value optimized out) at libusb1.c:275 #3 0x000801135763 in gp_port_free (port=0x80286d280) at gphoto2-port.c:124 #4 0x000800ebc6a9 in gp_abilities_list_detect (list=0x802869080, info_list=0x802869050, l=0x8028ec000, context=0x45) at gphoto2-abilities-list.c:488 #5 0x0040e0f7 in ?? () #6 0x00404aef in ?? () #7 0x000800635000 in ?? () #8 0x in ?? () Hi, This might be related - I get SIGBUS when running scanimage (Canon LIDE 110 scanner). I installed sane backends and frontends and xsane on 9.2-R, plugged in scanner. It is seen: ugen4.4: CanoScan Canon at usbus4, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON (500mA) scanimage -L gives: $ scanimage -L Bus error: 10 (core dumped) gdb gives: $ gdb scanimage GNU gdb 6.1.1 [FreeBSD] Copyright 2004 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type show copying to see the conditions. There is absolutely no warranty for GDB. Type show warranty for details. This GDB was configured as amd64-marcel-freebsd...(no debugging symbols found)... (gdb) r Starting program: /usr/local/bin/scanimage (no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...[New LWP 100431] [New Thread 804007400 (LWP 100431/scanimage)] Program received signal SIGBUS, Bus error. [Switching to Thread 804007400 (LWP 100431/scanimage)] 0x0008079d3829 in scsi_inquiry () from /usr/local/lib/sane/libsane-microtek2.so.1 I don't think it's a scanner issue as it works perfectly on windows and is completely supported on xsane. Maybe there's some kind of USB problem on freebsd-9, I dunno. -- John ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: gphoto2 bus error
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 frontends and xsane on 9.2-R, plugged in scanner. It is seen: ugen4.4: CanoScan Canon at usbus4, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON (500mA) scanimage -L gives: $ scanimage -L Bus error: 10 (core dumped) gdb gives: $ gdb scanimage GNU gdb 6.1.1 [FreeBSD] Copyright 2004 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type show copying to see the conditions. There is absolutely no warranty for GDB. Type show warranty for details. This GDB was configured as amd64-marcel-freebsd...(no debugging symbols found)... (gdb) r Starting program: /usr/local/bin/scanimage (no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...[New LWP 100431] [New Thread 804007400 (LWP 100431/scanimage)] Program received signal SIGBUS, Bus error. [Switching to Thread 804007400 (LWP 100431/scanimage)] 0x0008079d3829 in scsi_inquiry () from /usr/local/lib/sane/libsane-microtek2.so.1 I don't think it's a scanner issue as it works perfectly on windows and is completely supported on xsane. Maybe there's some kind of USB problem on freebsd-9, I dunno. Hi, Could you enter bt in GDB and show the output when this crash happens? --HPS ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: gphoto2 bus error
sorry, forgot to change From:, sending again On Tue, Oct 01, 2013 at 02:45:29PM +0100, John wrote: 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 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 () from /usr/local/lib/sane/libsane-microtek2.so.1 #1 0x0008063b384c in attach () from /usr/local/lib/sane/libsane-microtek2.so.1 #2 0x0008063b4a69 in attach_one () from /usr/local/lib/sane/libsane-microtek2.so.1 #3 0x00080083205b in sanei_scsi_find_devices () from /usr/local/lib/libsane.so.1 #4 0x00080082ef1e in sanei_config_attach_matching_devices () from /usr/local/lib/libsane.so.1 #5 0x0008063b4993 in sane_microtek2_init () from /usr/local/lib/sane/libsane-microtek2.so.1 #6 0x00080083acb4 in init () from /usr/local/lib/libsane.so.1 #7 0x00080083a944 in sane_dll_get_devices () from /usr/local/lib/libsane.so.1 #8 0x00402089 in ?? () #9 0x00401c41 in ?? () #10 0x000800628000 in ?? () #11 0x in ?? () (gdb) -- John -- John ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: gphoto2 bus error
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 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 () from /usr/local/lib/sane/libsane-microtek2.so.1 #1 0x0008063b384c in attach () from /usr/local/lib/sane/libsane-microtek2.so.1 #2 0x0008063b4a69 in attach_one () from /usr/local/lib/sane/libsane-microtek2.so.1 #3 0x00080083205b in sanei_scsi_find_devices () from /usr/local/lib/libsane.so.1 #4 0x00080082ef1e in sanei_config_attach_matching_devices () from /usr/local/lib/libsane.so.1 #5 0x0008063b4993 in sane_microtek2_init () from /usr/local/lib/sane/libsane-microtek2.so.1 #6 0x00080083acb4 in init () from /usr/local/lib/libsane.so.1 #7 0x00080083a944 in sane_dll_get_devices () from /usr/local/lib/libsane.so.1 #8 0x00402089 in ?? () #9 0x00401c41 in ?? () #10 0x000800628000 in ?? () #11 0x in ?? () (gdb) -- John ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: gphoto2 bus error
All code and libraries compiled from source. Yes, usbconfig show my photo, however gphoto crashed in both cases (with plugged photo and without). 2-3 month ago I updated system, and everything work fine... On Sunday 29 September 2013 13:21:38 Hans Petter Selasky wrote: Hi, Is all of your code and libraries compiled from source? Or do you have a mix? Are any gphoto compatible devices available when you type usbconfig ? --HPS -Original message- From:Artyom Mirgorodskiy artyom.mirgorod...@gmail.com mailto:artyom.mirgorod...@gmail.com Sent: Saturday 28th September 2013 19:45 To: Hans Petter Selasky hans.petter.sela...@bitfrost.no 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 :( Artyom MirgorodskiyOn Saturday 28 September 2013 19:05:16 wrote: Yes. I updated and reinstall all ports before report... Possible clang problems... On Saturday 28 September 2013 14:19:28 Hans Petter Selasky wrote: Hi, There has been no big changes in the FreeBSD's libusb recently. Looks like a problem in gphoto2. Did you upgrade to a newer gphoto2 version recently? --HPS -Original message- From:Artyom Mirgorodskiy artyom.mirgorod...@gmail.com mailto:artyom.mirgorod...@gmail.com mailto:artyom.mirgorod...@gmail.com mailto:artyom.mirgorod...@gmail.com Sent: Saturday 28th September 2013 1:05 To: freebsd-current@freebsd.org mailto:freebsd-current@freebsd.org mailto:freebsd-current@freebsd.org mailto:freebsd-current@freebsd.org Subject: gphoto2 bus error 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)] Program received signal SIGBUS, Bus error. [Switching to Thread 802806400 (LWP 100144/gphoto2)] 0x000801552597 in pthread_mutex_destroy () from /lib/libthr.so.3 (gdb) bt #0 0x000801552597 in pthread_mutex_destroy () from /lib/libthr.so.3 #1 0x0008040083cd in libusb_free_device_list () from /usr/lib/libusb.so.3 #2 0x000803801a2a in gp_port_usb_exit (port=value optimized out) at libusb1.c:275 #3 0x000801135763 in gp_port_free (port=0x80286d280) at gphoto2-port.c:124 #4 0x000800ebc6a9 in gp_abilities_list_detect (list=0x802869080, info_list=0x802869050, l=0x8028ec000, context=0x45) at gphoto2-abilities-list.c:488 #5 0x0040e0f7 in ?? () #6 0x00404aef in ?? () #7 0x000800635000 in ?? () #8 0x in ?? () -- Artyom Mirgorodskiy ___ freebsd-current@freebsd.org mailto:freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org mailto:freebsd-current-unsubscr...@freebsd.org -- Artyom Mirgorodskiy ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
RE: gphoto2 bus error
Hi, Is all of your code and libraries compiled from source? Or do you have a mix? Are any gphoto compatible devices available when you type usbconfig ? --HPS -Original message- From:Artyom Mirgorodskiy artyom.mirgorod...@gmail.com mailto:artyom.mirgorod...@gmail.com Sent: Saturday 28th September 2013 19:45 To: Hans Petter Selasky hans.petter.sela...@bitfrost.no 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 :( Artyom MirgorodskiyOn Saturday 28 September 2013 19:05:16 wrote: Yes. I updated and reinstall all ports before report... Possible clang problems... On Saturday 28 September 2013 14:19:28 Hans Petter Selasky wrote: Hi, There has been no big changes in the FreeBSD's libusb recently. Looks like a problem in gphoto2. Did you upgrade to a newer gphoto2 version recently? --HPS -Original message- From:Artyom Mirgorodskiy artyom.mirgorod...@gmail.com mailto:artyom.mirgorod...@gmail.com mailto:artyom.mirgorod...@gmail.com mailto:artyom.mirgorod...@gmail.com Sent: Saturday 28th September 2013 1:05 To: freebsd-current@freebsd.org mailto:freebsd-current@freebsd.org mailto:freebsd-current@freebsd.org mailto:freebsd-current@freebsd.org Subject: gphoto2 bus error 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)] Program received signal SIGBUS, Bus error. [Switching to Thread 802806400 (LWP 100144/gphoto2)] 0x000801552597 in pthread_mutex_destroy () from /lib/libthr.so.3 (gdb) bt #0 0x000801552597 in pthread_mutex_destroy () from /lib/libthr.so.3 #1 0x0008040083cd in libusb_free_device_list () from /usr/lib/libusb.so.3 #2 0x000803801a2a in gp_port_usb_exit (port=value optimized out) at libusb1.c:275 #3 0x000801135763 in gp_port_free (port=0x80286d280) at gphoto2-port.c:124 #4 0x000800ebc6a9 in gp_abilities_list_detect (list=0x802869080, info_list=0x802869050, l=0x8028ec000, context=0x45) at gphoto2-abilities-list.c:488 #5 0x0040e0f7 in ?? () #6 0x00404aef in ?? () #7 0x000800635000 in ?? () #8 0x in ?? () -- Artyom Mirgorodskiy ___ freebsd-current@freebsd.org mailto:freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org mailto:freebsd-current-unsubscr...@freebsd.org ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: gphoto2 bus error
Yes. I updated and reinstall all ports before report... Possible clang problems... On Saturday 28 September 2013 14:19:28 Hans Petter Selasky wrote: Hi, There has been no big changes in the FreeBSD's libusb recently. Looks like a problem in gphoto2. Did you upgrade to a newer gphoto2 version recently? --HPS -Original message- From:Artyom Mirgorodskiy artyom.mirgorod...@gmail.com 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 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)] Program received signal SIGBUS, Bus error. [Switching to Thread 802806400 (LWP 100144/gphoto2)] 0x000801552597 in pthread_mutex_destroy () from /lib/libthr.so.3 (gdb) bt #0 0x000801552597 in pthread_mutex_destroy () from /lib/libthr.so.3 #1 0x0008040083cd in libusb_free_device_list () from /usr/lib/libusb.so.3 #2 0x000803801a2a in gp_port_usb_exit (port=value optimized out) at libusb1.c:275 #3 0x000801135763 in gp_port_free (port=0x80286d280) at gphoto2-port.c:124 #4 0x000800ebc6a9 in gp_abilities_list_detect (list=0x802869080, info_list=0x802869050, l=0x8028ec000, context=0x45) at gphoto2-abilities-list.c:488 #5 0x0040e0f7 in ?? () #6 0x00404aef in ?? () #7 0x000800635000 in ?? () #8 0x in ?? () -- Artyom Mirgorodskiy ___ freebsd-current@freebsd.org mailto:freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org mailto:freebsd-current-unsubscr...@freebsd.org -- Artyom Mirgorodskiy ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: gphoto2 bus error
I try to build with gcc 4.6 - the same result :( Artyom MirgorodskiyOn Saturday 28 September 2013 19:05:16 wrote: Yes. I updated and reinstall all ports before report... Possible clang problems... On Saturday 28 September 2013 14:19:28 Hans Petter Selasky wrote: Hi, There has been no big changes in the FreeBSD's libusb recently. Looks like a problem in gphoto2. Did you upgrade to a newer gphoto2 version recently? --HPS -Original message- From:Artyom Mirgorodskiy artyom.mirgorod...@gmail.com 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 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)] Program received signal SIGBUS, Bus error. [Switching to Thread 802806400 (LWP 100144/gphoto2)] 0x000801552597 in pthread_mutex_destroy () from /lib/libthr.so.3 (gdb) bt #0 0x000801552597 in pthread_mutex_destroy () from /lib/libthr.so.3 #1 0x0008040083cd in libusb_free_device_list () from /usr/lib/libusb.so.3 #2 0x000803801a2a in gp_port_usb_exit (port=value optimized out) at libusb1.c:275 #3 0x000801135763 in gp_port_free (port=0x80286d280) at gphoto2-port.c:124 #4 0x000800ebc6a9 in gp_abilities_list_detect (list=0x802869080, info_list=0x802869050, l=0x8028ec000, context=0x45) at gphoto2-abilities-list.c:488 #5 0x0040e0f7 in ?? () #6 0x00404aef in ?? () #7 0x000800635000 in ?? () #8 0x in ?? () -- Artyom Mirgorodskiy ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
gphoto2 bus error
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)] Program received signal SIGBUS, Bus error. [Switching to Thread 802806400 (LWP 100144/gphoto2)] 0x000801552597 in pthread_mutex_destroy () from /lib/libthr.so.3 (gdb) bt #0 0x000801552597 in pthread_mutex_destroy () from /lib/libthr.so.3 #1 0x0008040083cd in libusb_free_device_list () from /usr/lib/libusb.so.3 #2 0x000803801a2a in gp_port_usb_exit (port=value optimized out) at libusb1.c:275 #3 0x000801135763 in gp_port_free (port=0x80286d280) at gphoto2-port.c:124 #4 0x000800ebc6a9 in gp_abilities_list_detect (list=0x802869080, info_list=0x802869050, l=0x8028ec000, context=0x45) at gphoto2-abilities-list.c:488 #5 0x0040e0f7 in ?? () #6 0x00404aef in ?? () #7 0x000800635000 in ?? () #8 0x in ?? () -- Artyom Mirgorodskiy ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: gpg-agent bus error (signal 10)
On Mon, 4 Apr 2011 09:57:13 +0400 Yuri Pankov yuri.pan...@gmail.com 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 all mental speculations…” (Sri Caitanya Mahaprabhu) http://atmarama.net | Hlapicina (Croatia) | GPG: 52B5C810 signature.asc Description: PGP signature
gpg-agent bus error (signal 10)
Hello! I've problem with keychain which cannot launch gpg-agent. Here is the result of the attempt to launch it: [gour@atmarama gour] gpg-agent --verbose --debug guru --daemon gpg-agent[80588]: reading options from `/home/gour/.gnupg/gpg-agent.conf' gpg-agent[80588]: enabled debug 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 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 I've installed gnupg-2.0.17_1 from the ports and my system is: FreeBSD 9.0-CURRENT on x86_64. Any idea? Sincerely, Gour -- “In the material world, conceptions of good and bad are all mental speculations…” (Sri Caitanya Mahaprabhu) http://atmarama.net | Hlapicina (Croatia) | GPG: 52B5C810 signature.asc Description: PGP signature
Re: gpg-agent bus error (signal 10)
On Sun, Apr 03, 2011 at 08:41:57PM +0200, Gour-Gadadhara Dasa wrote: Hello! I've problem with keychain which cannot launch gpg-agent. Here is the result of the attempt to launch it: [gour@atmarama gour] gpg-agent --verbose --debug guru --daemon gpg-agent[80588]: reading options from `/home/gour/.gnupg/gpg-agent.conf' gpg-agent[80588]: enabled debug 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 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 I've installed gnupg-2.0.17_1 from the ports and my system is: FreeBSD 9.0-CURRENT on x86_64. Any idea? Sincerely, Gour -- “In the material world, conceptions of good and bad are all mental speculations…” (Sri Caitanya Mahaprabhu) http://atmarama.net | Hlapicina (Croatia) | GPG: 52B5C810 http://lists.freebsd.org/pipermail/freebsd-ports/2011-March/066146.html The workaround is `ln -sf j /etc/malloc.conf`. HTH, Yuri ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Yoics! Just upgraded and cc is (mostly) bus-error-ing on buildworld.
on 29/05/2010 10:47 Andrew Reilly said the following: Just to prefix with my config: FreeBSD duncan.reilly.home 9.0-CURRENT FreeBSD 9.0-CURRENT #7: Sat May 29 11:20:54 EST 2010 r...@duncan.reilly.home:/nb/obj/nb/src/sys/DUNCAN amd64 Current source tree was csupped about half an hour ago. I don't think that my hardware has gone 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 report, with preprocessed source if appropriate. See URL:http://gcc.gnu.org/bugs.html for instructions. *** Error code 1 Stop in /nb/src/cddl/usr.bin/sgsmsg. Also, if I run buildworld with -j4 (my usual config), then a different compile crashes the same way : /nb/src/cddl/usr.bin/sgsmsg/../../../cddl/contrib/opensolaris/cmd/sgs/tools/common/string_table.c:467: internal compiler error: Bus error: 10 but in that case it was not the first compile which broke, and several (parallel, I assume) broke at the same time. So: is anyone else seeing this? Is it likely that heisenbugs have found their way into the compiler in the last week, or perhaps in the kernel's page table handling code? Have you been playing with clang or other alternative compilers? If not, then I think that it's your hardware. -- Andriy Gapon ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Yoics! Just upgraded and cc is (mostly) bus-error-ing on buildworld.
On Mon, 31 May 2010 16:30:04 +0300
Andriy Gapon a...@icyb.net.ua 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. Compiler crashes are usually fix the
hardware problems. I'm not so sure any more: I restored /boot
and /usr/{not local or home} from backup from about a week ago,
and using that compiler on the same hardware, I was able to get a
build and install to complete without problem. Heisenbug
somewhere, perhaps? The other hit against the hardware problem
suggestion is that the failure was in specific, repeatable places
in certain system source files. I could compile a chunk of my
own code without problems, though.
I'm now on:
FreeBSD duncan.reilly.home 9.0-CURRENT FreeBSD 9.0-CURRENT #0: Mon May 31
02:39:59 EST 2010 r...@duncan.reilly.home:/nb/obj/nb/src/sys/DUNCAN amd64
based on a csup from the australian mirror from yesterday morning
(or perhaps Sunday night), and it all seems to be back to normal.
Very odd.
Cheers,
--
Andrew
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Yoics! Just upgraded and cc is (mostly) bus-error-ing on buildworld.
On Mon, May 31, 2010 at 9:06 PM, Andrew Reilly arei...@bigpond.net.au wrote:
On Mon, 31 May 2010 16:30:04 +0300
Andriy Gapon a...@icyb.net.ua 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 _is_ your make.conf though?
If not, then I think that it's your hardware.
I did too at first. Compiler crashes are usually fix the
hardware problems. I'm not so sure any more: I restored /boot
and /usr/{not local or home} from backup from about a week ago,
and using that compiler on the same hardware, I was able to get a
build and install to complete without problem. Heisenbug
somewhere, perhaps? The other hit against the hardware problem
suggestion is that the failure was in specific, repeatable places
in certain system source files. I could compile a chunk of my
own code without problems, though.
I'm now on:
FreeBSD duncan.reilly.home 9.0-CURRENT FreeBSD 9.0-CURRENT #0: Mon May 31
02:39:59 EST 2010 r...@duncan.reilly.home:/nb/obj/nb/src/sys/DUNCAN amd64
based on a csup from the australian mirror from yesterday morning
(or perhaps Sunday night), and it all seems to be back to normal.
Thanks,
-Garrett
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Yoics! Just upgraded and cc is (mostly) bus-error-ing on buildworld.
On Mon, 31 May 2010 21:17:41 -0700 Garrett Cooper yanef...@gmail.com 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/ports PORTSSUPFILE=/root/ports-supfile SUPFILE=/root/standard-supfile SUPHOST=cvs.au.freebsd.org SUP_UPDATE=yes SUP=cvsup # OOo needs a really large TMPDIR, use this for OOo: TMPDIR=/nb/tmp/ # added by use.perl 2010-05-15 17:53:15 PERL_VERSION=5.10.1 my DUNCAN kern conf is just: include GENERIC ident DUNCAN It used to have more frobs in it than that! Just in case it matters: the kernel/userland/cc that was giving me grief had been built with a make.conf that said NO_KERBEROS=yes, something I'd added to try to work around the MD2_foo crypto linking problems. I can't imagine why that would be a problem, but I'm not risking it any more... Cheers, -- Andrew ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Yoics! Just upgraded and cc is (mostly) bus-error-ing on buildworld.
On Mon, May 31, 2010 at 9:28 PM, Andrew Reilly arei...@bigpond.net.au wrote: On Mon, 31 May 2010 21:17:41 -0700 Garrett Cooper yanef...@gmail.com 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/ports PORTSSUPFILE=/root/ports-supfile SUPFILE=/root/standard-supfile SUPHOST=cvs.au.freebsd.org SUP_UPDATE=yes SUP=cvsup # OOo needs a really large TMPDIR, use this for OOo: TMPDIR=/nb/tmp/ # added by use.perl 2010-05-15 17:53:15 PERL_VERSION=5.10.1 my DUNCAN kern conf is just: include GENERIC ident DUNCAN It used to have more frobs in it than that! Just in case it matters: the kernel/userland/cc that was giving me grief had been built with a make.conf that said NO_KERBEROS=yes, something I'd added to try to work around the MD2_foo crypto linking problems. I can't imagine why that would be a problem, but I'm not risking it any more... 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? Thanks, -Garrett ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Yoics! Just upgraded and cc is (mostly) bus-error-ing on buildworld.
Hi Garrett, On Mon, 31 May 2010 21:36:23 -0700 Garrett Cooper yanef...@gmail.com 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 ever have (compiled with clang). I did pull the pieces together when Roman first suggested it, but it didn't work then, and I need this machine to be more up than down, so I've shelved it for a while. At that time clang also had a bug that was a show-stopper for me, in that it wouldn't compile my own code (compile time constant expressions with conditionals were not recognised as constant, or something like that.) Long since fixed, but I don't have enough time to keep up. I do regularly nuke /usr/obj before rebuilding. Not always, but often. Cheers, -- Andrew ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Yoics! Just upgraded and cc is (mostly) bus-error-ing on buildworld.
Just to prefix with my config: FreeBSD duncan.reilly.home 9.0-CURRENT FreeBSD 9.0-CURRENT #7: Sat May 29 11:20:54 EST 2010 r...@duncan.reilly.home:/nb/obj/nb/src/sys/DUNCAN amd64 Current source tree was csupped about half an hour ago. I don't think that my hardware has gone 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 report, with preprocessed source if appropriate. See URL:http://gcc.gnu.org/bugs.html for instructions. *** Error code 1 Stop in /nb/src/cddl/usr.bin/sgsmsg. Also, if I run buildworld with -j4 (my usual config), then a different compile crashes the same way : /nb/src/cddl/usr.bin/sgsmsg/../../../cddl/contrib/opensolaris/cmd/sgs/tools/common/string_table.c:467: internal compiler error: Bus error: 10 but in that case it was not the first compile which broke, and several (parallel, I assume) broke at the same time. So: is anyone else seeing this? Is it likely that heisenbugs have found their way into the compiler in the last week, or perhaps in the kernel's page table handling code? More importantly: any thoughts about how I can proceed from here? Re-install from a snapshot? Cheers, -- Andrew ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Bus error
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 # set CFLAGS=$CFLAGS -g # make # install -o root -g wheel -m 4555 -fschg /usr/obj/usr/src/usr.bin/su/su /usr/bin ( 'make install' will strip the binary and all the nice debug info is gone) Now run su in the debugger, and will probably get a core dump: gdb /usr/bin/su GNU gdb 5.2.1 (FreeBSD) Copyright 2002 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type show copying to see the conditions. There is absolutely no warranty for GDB. Type show warranty for details. This GDB was configured as i386-undermydesk-freebsd...(no debugging symbols found)... (gdb) run Starting program: /usr/bin/su When it crashes, get a backtrace (in gdb: `bt full' and post it here). Simon signature.asc Description: Digital signature
Re: Bus error
# set CFLAGS=$CFLAGS -g # make Arg! Please use # make CFLAGS='-O -g' instead. signature.asc Description: Digital signature
Re: Bus error
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) What CFLAGS do you have in /etc/make.conf? 3) Is your kernel in sync with your userland? 4) Have you run mergemaster since the last round of PAM changes? Regards, Andre Guibert de Bruet | Enterprise Software Consultant Silicon Landmark, LLC. | http://siliconlandmark.com/ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Bus error
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 line between sanaty and insanaty, i walk that line . ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
FreeBSD 5.1 Release: Enlightenment BUS ERROR
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 another TTY, also as root. then startx and ran the enlightenment configuration. then changed the theme, background and turned off tooltips. Then reduced the virtual desktop from two to one. Then attempted to reduce the multiple desktops from two to one and this caused a bus error in enlightenment. Enlightenment caught the error, reported it in a dialog box which said this was highly unusual and allowed me to gracefully shut E down. I tried it again, startx again works fine. The virtual screen settings had been saved correctly by enlightenment. Then I tried to reduce multiple desktops from two to one again. Ths resulted ina bus error, again. Then I waited until mozilla was finished compiling and tried the same action again. Again same bus error. ___ Join Excite! - http://www.excite.com The most personalized portal on the Web! ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
RC3 with JDK1.3.1 cause bus error core dump
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
===snip=
import java.net.*;
public class CrashBSD
{
static public void main( String args[] )
{
try
{
ServerSocket ss = new ServerSocket( 0, 4 );
System.out.println( ss );
}
catch ( Exception e ) { System.out.println( e );
System.exit( 1 ); }
}
}
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
Re: natd core dumping with bus error
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 core dumps with a bus error. I think this started JUST BEFORE the KSE commit. 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): luigi 2002/06/27 16:02:18 PDT Modified files: sbin/ipfwMakefile sys/netinet ip_dummynet.c ip_fw.h sys/conf files lib/libalias alias_db.c Added files: sbin/ipfwipfw2.c sys/netinet ip_fw2.c Log: The new ipfw code. I upgraded my pre-KSE kernel and system to the latest versions of these files, and recompiled natd, ipfw, libalias, and the kernel. natd is now stable. The firewall rules appear to be working correctly as well (I started temporarily logging most packets, and the log files show that the packets are accepted/denied as indicated by the rules I gave it). -- Richard Seaman, Jr.email:[EMAIL PROTECTED] 5182 N. Maple Lane phone:262-367-5450 Nashotah WI 53058fax:262-367-5852 To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: natd core dumping with bus error
Could you clarify the problem ? I believe the problem appears when you _do_ use punch_fw, otherwise the modified code is never called. cheers luigi 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 core dumps with a bus error. I think this started JUST BEFORE the KSE commit. 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): luigi 2002/06/27 16:02:18 PDT Modified files: sbin/ipfwMakefile sys/netinet ip_dummynet.c ip_fw.h sys/conf files lib/libalias alias_db.c Added files: sbin/ipfwipfw2.c sys/netinet ip_fw2.c Log: The new ipfw code. -- Richard Seaman, Jr.email:[EMAIL PROTECTED] 5182 N. Maple Lane phone:262-367-5450 Nashotah WI 53058fax:262-367-5852 To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: natd core dumping with bus error
I started out without punch_fw. natd was core dumping on me. I eventually figured out that if I added punch_fw in, natd no longer core dumped. I've left it in, things seem to work better anyway with it in. I've put a core dump file at http://outel.org/natd.core Here 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. comment out the punch_fw option and it core dumps) use_sockets yes same_ports yes unregistered_only yes interface rl0 punch_fw5000:50 natd stuff in /etc/rc.conf: natd_enable=YES natd_flags=-f /etc/natd.conf natd_interface=rl0 # rl0-external ifc : fxp0-internal ifc ipfw list: ( this is the SIMPLE firewall type rules with the addition of rules 400 and 500 ) 00100 allow ip from any to any via lo0 00200 deny ip from any to 127.0.0.0/8 00300 deny ip from 127.0.0.0/8 to any 00400 allow tcp from any to any via fxp0 00500 allow udp from any to any via fxp0 00600 deny ip from 192.168.1.0/24 to any in via rl0 00700 deny ip from 168.150.177.152 to any in via fxp0 00800 deny ip from any to 10.0.0.0/8 via rl0 00900 deny ip from any to 172.16.0.0/12 via rl0 01000 deny ip from any to 192.168.0.0/16 via rl0 01100 deny ip from any to 0.0.0.0/8 via rl0 01200 deny ip from any to 169.254.0.0/16 via rl0 01300 deny ip from any to 192.0.2.0/24 via rl0 01400 deny ip from any to 224.0.0.0/4 via rl0 01500 deny ip from any to 240.0.0.0/4 via rl0 01600 divert 8668 ip from any to any via rl0 01700 deny ip from 10.0.0.0/8 to any via rl0 01800 deny ip from 172.16.0.0/12 to any via rl0 01900 deny ip from 192.168.0.0/16 to any via rl0 02000 deny ip from 0.0.0.0/8 to any via rl0 02100 deny ip from 169.254.0.0/16 to any via rl0 02200 deny ip from 192.0.2.0/24 to any via rl0 02300 deny ip from 224.0.0.0/4 to any via rl0 02400 deny ip from 240.0.0.0/4 to any via rl0 02500 allow tcp from any to any established 02600 allow ip from any to any frag 02700 allow tcp from any to 168.150.177.152 25 setup 02800 allow tcp from any to 168.150.177.152 53 setup 02900 allow udp from any to 168.150.177.152 53 03000 allow udp from 168.150.177.152 53 to any 03100 allow tcp from any to 168.150.177.152 80 setup 03200 deny log tcp from any to any in via rl0 setup 03300 allow tcp from any to any setup 03400 allow udp from 168.150.177.152 to any 53 keep-state 65535 deny ip from any to any gdb traceback: su-2.05# gdb -c natd.core /sbin/natd GNU gdb 5.2.0 (FreeBSD) 20020627 Copyright 2002 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type show copying to see the conditions. There is absolutely no warranty for GDB. Type show warranty for details. This GDB was configured as i386-undermydesk-freebsd...(no debugging symbols found)... Core was generated by `natd'. Program terminated with signal 10, Bus error. # 0 0x08050c27 in ?? () (gdb) bt # 0 0x08050c27 in ?? () # 1 0x0804f0f0 in ?? () # 2 0x0804f0a6 in ?? () # 3 0x080503b5 in ?? () # 4 0x0804b489 in ?? () # 5 0x08048b38 in ?? () # 6 0x080487ee in ?? () # 7 0x08048131 in ?? () (gdb) If you need something else to diagnose this let me know and I'll do whatever I can to help. --On Monday, July 08, 2002 2:26 AM -0700 Luigi Rizzo [EMAIL PROTECTED] wrote: Could you clarify the problem ? I believe the problem appears when you _do_ use punch_fw, otherwise the modified code is never called. cheers luigi 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 core dumps with a bus error. I think this started JUST BEFORE the KSE commit. 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): luigi 2002/06/27 16:02:18 PDT Modified files: sbin/ipfwMakefile sys/netinet ip_dummynet.c ip_fw.h sys/conf files lib/libalias alias_db.c Added files: sbin/ipfwipfw2.c sys/netinet ip_fw2.c Log: The new ipfw code. -- Richard Seaman, Jr.email:[EMAIL PROTECTED] 5182 N. Maple Lane phone:262-367-5450 Nashotah WI 53058fax:262-367-5852 To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: natd core dumping with bus error
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 - Original Message - From: Richard Seaman, Jr. [EMAIL PROTECTED] To: Luigi Rizzo [EMAIL PROTECTED] Cc: 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 problem appears when you _do_ use punch_fw, otherwise the modified code is never called. cheers luigi I did not have punch_fw enabled when I encountered 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? -- Richard Seaman, Jr.email:[EMAIL PROTECTED] 5182 N. Maple Lane phone:262-367-5450 Nashotah WI 53058fax:262-367-5852 To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message __ Do You Yahoo!? Sign up for SBC Yahoo! Dial - First Month Free http://sbc.yahoo.com To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: natd core dumping with bus error
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 net.inet.ip.forwarding: 1 net.inet.ip.fastforwarding: 0 net.inet6.ip6.forwarding: 0 Everything works fine with pre new-ipfw, and has for years. Same rules, same configuration, and with new ipfw, core dump. -- Richard Seaman, Jr.email:[EMAIL PROTECTED] 5182 N. Maple Lane phone:262-367-5450 Nashotah WI 53058fax:262-367-5852 To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: natd core dumping with bus error
--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 Well, I'm not running ppp, and never indicated I was. I'm running natd. # sysctl -a | grep forward net.inet.ip.forwarding: 1 net.inet.ip.fastforwarding: 0 net.inet6.ip6.forwarding: 0 Everything works fine with pre new-ipfw, and has for years. Same rules, same configuration, and with new ipfw, core dump. Same scenario here with a cvsup build from about 16:00 GMT yesterday. Defining #NO_FW_PUNCH (primarily for libalias) and placing a #ifndef NO_FW_PUNCH around the code in natd.c:SetupPunchFWHole fixed the problem for me. I can look into this further near the end of this week. -- Kenn Martin [EMAIL PROTECTED] voice/fax: 877 594 3375 To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: natd core dumping with bus error
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. The problem still exits. It isn't an instant dump, it runs for a while. Right. Typically 30secs - 5 mins before it dumped. And when I ran natd in verbose mode, it showed quite a few packets in and out before it dumped. -- Richard Seaman, Jr.email:[EMAIL PROTECTED] 5182 N. Maple Lane phone:262-367-5450 Nashotah WI 53058fax:262-367-5852 To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: natd core dumping with bus error
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 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. The problem still exits. It isn't an instant dump, it runs for a while. Right. Typically 30secs - 5 mins before it dumped. And when I ran natd in verbose mode, it showed quite a few packets in and out before it dumped. -- Richard Seaman, Jr.email:[EMAIL PROTECTED] 5182 N. Maple Lane phone:262-367-5450 Nashotah WI 53058fax:262-367-5852 To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: natd core dumping with bus error
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 file and recompiling libalias and natd fixes the natd breakage for me. However, I was seeing some possible side effect of this (see my earlier mail about deny rules not working in ipfw) but I am not sure since I have at least one other report of this. -- Regards: Szilveszter ADAM Szombathely Hungary To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: natd core dumping with bus error
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 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 net.inet.ip.forwarding: 1 net.inet.ip.fastforwarding: 0 net.inet6.ip6.forwarding: 0 Everything works fine with pre new-ipfw, and has for years. Same rules, same configuration, and with new ipfw, core dump. -- Richard Seaman, Jr.email:[EMAIL PROTECTED] 5182 N. Maple Lane phone:262-367-5450 Nashotah WI 53058fax:262-367-5852 __ Do You Yahoo!? Sign up for SBC Yahoo! Dial - First Month Free http://sbc.yahoo.com To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: natd core dumping with bus error
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'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): luigi 2002/06/27 16:02:18 PDT Modified files: sbin/ipfwMakefile sys/netinet ip_dummynet.c ip_fw.h sys/conf files lib/libalias alias_db.c Added files: sbin/ipfwipfw2.c sys/netinet ip_fw2.c Log: The new ipfw code. -- Richard Seaman, Jr.email:[EMAIL PROTECTED] 5182 N. Maple Lane phone:262-367-5450 Nashotah WI 53058fax:262-367-5852 To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: natd core dumping with bus error
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 core dumps with a bus error. I think this started JUST BEFORE the KSE commit. 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): I will look into it later this week if Luigi does not beat me to it. luigi 2002/06/27 16:02:18 PDT Modified files: sbin/ipfwMakefile sys/netinet ip_dummynet.c ip_fw.h sys/conf files lib/libalias alias_db.c Added files: sbin/ipfwipfw2.c sys/netinet ip_fw2.c Log: The new ipfw code. -- Richard Seaman, Jr.email:[EMAIL PROTECTED] 5182 N. Maple Lane phone:262-367-5450 Nashotah WI 53058fax:262-367-5852 To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message -- Ruslan Ermilov Sysadmin and DBA, [EMAIL PROTECTED] Sunbay Software AG, [EMAIL PROTECTED] FreeBSD committer, +380.652.512.251Simferopol, Ukraine http://www.FreeBSD.org The Power To Serve http://www.oracle.com Enabling The Information Age msg40468/pgp0.pgp Description: PGP signature
natd core dumping with bus error
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 and it core dumps) use_sockets yes same_ports yes unregistered_only yes interface rl0 punch_fw5000:50 natd stuff in /etc/rc.conf: natd_enable=YES natd_flags=-f /etc/natd.conf natd_interface=rl0# rl0-external ifc : fxp0-internal ifc ipfw list: ( this is the SIMPLE firewall type rules with the addition of rules 400 and 500 ) 00100 allow ip from any to any via lo0 00200 deny ip from any to 127.0.0.0/8 00300 deny ip from 127.0.0.0/8 to any 00400 allow tcp from any to any via fxp0 00500 allow udp from any to any via fxp0 00600 deny ip from 192.168.1.0/24 to any in via rl0 00700 deny ip from 168.150.177.152 to any in via fxp0 00800 deny ip from any to 10.0.0.0/8 via rl0 00900 deny ip from any to 172.16.0.0/12 via rl0 01000 deny ip from any to 192.168.0.0/16 via rl0 01100 deny ip from any to 0.0.0.0/8 via rl0 01200 deny ip from any to 169.254.0.0/16 via rl0 01300 deny ip from any to 192.0.2.0/24 via rl0 01400 deny ip from any to 224.0.0.0/4 via rl0 01500 deny ip from any to 240.0.0.0/4 via rl0 01600 divert 8668 ip from any to any via rl0 01700 deny ip from 10.0.0.0/8 to any via rl0 01800 deny ip from 172.16.0.0/12 to any via rl0 01900 deny ip from 192.168.0.0/16 to any via rl0 02000 deny ip from 0.0.0.0/8 to any via rl0 02100 deny ip from 169.254.0.0/16 to any via rl0 02200 deny ip from 192.0.2.0/24 to any via rl0 02300 deny ip from 224.0.0.0/4 to any via rl0 02400 deny ip from 240.0.0.0/4 to any via rl0 02500 allow tcp from any to any established 02600 allow ip from any to any frag 02700 allow tcp from any to 168.150.177.152 25 setup 02800 allow tcp from any to 168.150.177.152 53 setup 02900 allow udp from any to 168.150.177.152 53 03000 allow udp from 168.150.177.152 53 to any 03100 allow tcp from any to 168.150.177.152 80 setup 03200 deny log tcp from any to any in via rl0 setup 03300 allow tcp from any to any setup 03400 allow udp from 168.150.177.152 to any 53 keep-state 65535 deny ip from any to any gdb traceback: su-2.05# gdb -c natd.core /sbin/natd GNU gdb 5.2.0 (FreeBSD) 20020627 Copyright 2002 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type show copying to see the conditions. There is absolutely no warranty for GDB. Type show warranty for details. This GDB was configured as i386-undermydesk-freebsd...(no debugging symbols found)... Core was generated by `natd'. Program terminated with signal 10, Bus error. #0 0x08050c27 in ?? () (gdb) bt #0 0x08050c27 in ?? () #1 0x0804f0f0 in ?? () #2 0x0804f0a6 in ?? () #3 0x080503b5 in ?? () #4 0x0804b489 in ?? () #5 0x08048b38 in ?? () #6 0x080487ee in ?? () #7 0x08048131 in ?? () (gdb) If you need something else to diagnose this let me know and I'll do whatever I can to help. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Bus error compiling thefish 0.2 on -current
Hi, I'm finishing the new version of sysutils/thefish, and doing some development on a -current box. For the ncurses/dialog frontend, I'm using a couple of functions from the sysinstall code, and this program works perfectly well on a 4.5-STABLE system. If I take the binary and 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 these: flynn@saioa# uname -a FreeBSD saioa.energyhq.tk 5.0-CURRENT FreeBSD 5.0-CURRENT #0: Sat Mar 30 00:37:49 GMT 2002 root@:/usr/obj/usr/src/sys/SAIOA i386 flynn@saioa# cc -v Using builtin specs. gcc version 2.95.4 20020320 [FreeBSD] The gdb trace when the program fails: (gdb) bt #0 0x280da10a in dialog_menu () from /usr/lib/libdialog.so.4 #1 0x804e0a7 in dmenuOpen (menu=0x81d5000, choice=0xbfbff8bc, scroll=0xbfbff8c0, curr=0xbfbff8c4, max=0xbfbff8c8, buttons=0) at ncurses_ui.c:249 #2 0x804df6a in dmenuOpenSimple (menu=0x81d5000, buttons=0) at ncurses_ui.c:191 #3 0x804deff in dmenuSubmenu (tmp=0x80bb6f4) at ncurses_ui.c:175 #4 0x280db1ae in dialog_menu () from /usr/lib/libdialog.so.4 #5 0x804e0a7 in dmenuOpen (menu=0x80bb680,choice=0xbfbffa5c, scroll=0xbfbffa60, curr=0xbfbffa64, max=0xbfbffa68,buttons=1) at ncurses_ui.c:249 #6 0x804debf in create_ncurses_ui(rc_knobs=0x817b000, num_knobs=96, rc_strings=0x8197000, num_str=138) at ncurses_ui.c:163 #7 0x804b2ed in main (argc=0, argv=0xbfbffb18) at main.c:216 #8 0x804a5c5 in _start () (gdb) The program tarball can be found at http://energyhq.homeip.net/files/thefish-0.2.tar.gz My question is, is it a bug in my program that only shows in -CURRENT or is the compiler in current broken? Cheers, -- Miguel Mendez - [EMAIL PROTECTED] GPG Public Key :: http://energyhq.homeip.net/files/pubkey.txt EnergyHQ :: http://www.energyhq.tk FreeBSD - The power to serve! msg36776/pgp0.pgp Description: PGP signature
Re: Bus error compiling thefish 0.2 on -current
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://energyhq.homeip.net/files/pubkey.txt EnergyHQ :: http://www.energyhq.tk FreeBSD - The power to serve! msg36788/pgp0.pgp Description: PGP signature
Re: Bus error compiling thefish 0.2 on -current
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. You may want to try an older version of the code to see if that's it, and then talk to Eric Melville, if it is. -- Terry To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Bus error compiling thefish 0.2 on -current
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 could be the malloc.conf defaults on -current exposing a bug in the program code. Kris msg36802/pgp0.pgp Description: PGP signature
Re: Bus error compiling thefish 0.2 on -current
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 memory is zeroed, which would explain why the program worked when linked with efence. I've built a debug version of libdialog and found something interesting... #0 0x28324253 in dialog_checklist (title=0x80bcf54 Knobs Menu, prompt=0x80bcf60 A checked entry means that knob is set to YES, height=-1,width=-1, list_height=15, cnt=-1697, it=0x81e6014, result=0x0) at checklist.c:82 82 status[i] = ditems[i].checked ? ditems[i].checked(ditems[i]) : FALSE; There is something odd in that cnt value, as there aren't 1697 entries in the menu. The problem is the way the dialog structure is built, I malloc memory but don't zero it, so when I call the function that in the end calls dialog, it erroneously assumes that there are more entries than there really are, since it simply checks for !=0 data. The garbage present in the malloc'ed mem is the cause. Why this problem doesn't show on -STABLE is still beyond my comprehension, default malloc behaviour maybe? Anyway, problem solved, thanks for all. Cheers, -- Miguel Mendez - [EMAIL PROTECTED] GPG Public Key :: http://energyhq.homeip.net/files/pubkey.txt EnergyHQ :: http://www.energyhq.tk FreeBSD - The power to serve! msg36803/pgp0.pgp Description: PGP signature
Re: Bus error compiling thefish 0.2 on -current
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 for maximum debugging, at the expense of performance, but it helps people catch bugs like this. -garrett -- garrett rooneyRemember, any design flaw you're [EMAIL PROTECTED] sufficiently snide about becomes http://electricjellyfish.net/ a feature. -- Dan Sugalski To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Bus error compiling thefish 0.2 on -current
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 narrow the problem to libc? Any ideas? Sounds like it could be the malloc.conf defaults on -current exposing a bug in the program code. BTW, you set efence to fill memory like -current's malloc by setting the environment variable EF_FILL to 208. -- Dan Nelson [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Bus error on savecore
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 dumping core on a bus error, but that was prior to yesterday's make world. It was when I was su root, using passwd to change a user's password, i.e. passwd user. The core dump came just before the point where the command would have exited anyways. -Donn To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Bus error on savecore
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. Works now. Thanks! Blaz Zupan, Medinet d.o.o, Linhartova 21, 2000 Maribor, Slovenia E-mail: [EMAIL PROTECTED], Tel: +386-2-320-6320, Fax: +386-2-320-6325 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Bus error on savecore
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, Slovenia E-mail: [EMAIL PROTECTED], Tel: +386-2-320-6320, Fax: +386-2-320-6325 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Bus error in isatty() from /usr/lib/libc.so.3
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 else, any pointers on what I might do next would be great. [...] #1 0x2818db22 in isatty () from /usr/lib/libc.so.3 #2 0x2818e1de in malloc () from /usr/lib/libc.so.3 #3 0x28236e88 in _thread_fd_table_init () from /usr/lib/libc_r.so.4 #4 0x28238056 in _thread_fd_lock_debug () from /usr/lib/libc_r.so.4 You are linking against both libc _and_ libc_r. "Don't do that!" -- John Birrell - [EMAIL PROTECTED]; [EMAIL PROTECTED] http://www.cimlogic.com.au/ CIMlogic Pty Ltd, GPO Box 117A, Melbourne Vic 3001, Australia +61 418 353 137 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Bus error in isatty() from /usr/lib/libc.so.3
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 else,
any pointers on what I might do next would be great.
Thanks,
Tim
How to repeat:
I installed MySQL 3.23.2, then DBI-1.11. I compiled
Msql-Mysql-modules-1.2200, and ran the test suite. All but the first
test dumped core, all with this same error.
This is with -CURRENT as of Aug 10 @ 7AM (GMT). I did a complete
make buildworld; make installworld;, then I recompiled the kernel.
tim@threads$ uname -a
FreeBSD threads.polyesthetic.org 4.0-CURRENT FreeBSD 4.0-CURRENT #11: Wed Aug 11
08:57:53 MST 1999 [EMAIL PROTECTED]:/usr/src/sys/compile/THREADS i386
tim@threads:/usr/local/src/Msql-Mysql-modules-1.2200/mysql$
LD_LIBRARY_PATH=`pwd`/../blib/arch/auto/DBD/mysql gdb /usr/bin/perl
GNU gdb 4.18
Copyright 1998 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB. Type "show warranty" for details.
This GDB was configured as "i386-unknown-freebsd"...
(no debugging symbols found)...
(gdb) run -I../blib/lib t/10dsnlist.t
Starting program: /usr/bin/perl -I../blib/lib t/10dsnlist.t
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
Driver is mysql
1..3
(no debugging symbols found)...(no debugging symbols found)...
_login('database=test' 'tim' '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 /usr/lib/libc.so.3
#3 0x28236e88 in _thread_fd_table_init () from /usr/lib/libc_r.so.4
#4 0x28238056 in _thread_fd_lock_debug () from /usr/lib/libc_r.so.4
#5 0x28248498 in bind () from /usr/lib/libc_r.so.4
#6 0x2818eeb7 in .cerror () from /usr/lib/libc.so.3
#7 0x28238056 in _thread_fd_lock_debug () from /usr/lib/libc_r.so.4
#8 0x28248498 in bind () from /usr/lib/libc_r.so.4
#9 0x2818eeb7 in .cerror () from /usr/lib/libc.so.3
#10 0x28238056 in _thread_fd_lock_debug () from /usr/lib/libc_r.so.4
#26905 0x28238056 in _thread_fd_lock_debug () from /usr/lib/libc_r.so.4
#26906 0x28248498 in bind () from /usr/lib/libc_r.so.4
#26907 0x2818eeb7 in .cerror () from /usr/lib/libc.so.3
#26908 0x281dbb95 in my_net_init (net=0x8057c54, nettype=NET_TYPE_SOCKET,
fd=5, pipe=0x0) at net.c:137
#26909 0x281d97be in mysql_real_connect (mysql=0x8057c54,
host=0x281e5bf0 "localhost", user=0x81283d0 "tim",
passwd=0x8128650 "ign0rant", db=0x8108650 "test", port=0,
unix_socket=0x281e5b80 "/tmp/mysql.sock", client_flag=0) at libmysql.c:1194
#26910 0x281c0ba2 in mysql_dr_connect ()
from
/usr/local/src/Msql-Mysql-modules-1.2200/mysql/../blib/arch/auto/DBD/mysql/mysql.so
#26911 0x281c130e in _MyLogin ()
from
/usr/local/src/Msql-Mysql-modules-1.2200/mysql/../blib/arch/auto/DBD/mysql/mysql.so
#26912 0x281c139d in mysql_db_login ()
from
/usr/local/src/Msql-Mysql-modules-1.2200/mysql/../blib/arch/auto/DBD/mysql/mysql.so
#26913 0x281c90cd in XS_DBD__mysql__db__login ()
from
/usr/local/src/Msql-Mysql-modules-1.2200/mysql/../blib/arch/auto/DBD/mysql/mysql.so
#26914 0x280af0b5 in Perl_pp_entersub () from /usr/lib/libperl.so.3
#26915 0x28079d69 in Perl_runops_standard () from /usr/lib/libperl.so.3
#26916 0x280e0519 in perl_call_sv () from /usr/lib/libperl.so.3
#26917 0x281b16a5 in XS_DBI_dispatch ()
from /usr/local/lib/perl5/site_perl/5.005/i386-freebsd/auto/DBI/DBI.so
#26918 0x280af0b5 in Perl_pp_entersub () from /usr/lib/libperl.so.3
#26919 0x28079d69 in Perl_runops_standard () from /usr/lib/libperl.so.3
#26920 0x280dfd6e in perl_run () from /usr/lib/libperl.so.3
#26921 0x8048da8 in perl_free ()
#26922 0x8048cd5 in perl_free ()
(gdb)
Summary of my perl5 (5.0 patchlevel 5 subversion 3) configuration:
Platform:
osname=freebsd, osvers=4.0-current, archname=i386-freebsd
uname='freebsd freefall.freebsd.org 4.0-current freebsd 4.0-current #0: $Date:
1999/05/05 19:09:48 $'
hint=recommended, useposix=true, d_sigaction=define
usethreads=undef useperlio=undef d_sfio=undef
Compiler:
cc='cc', optimize='undef', gccversion=egcs-2.91.66 19990314 (egcs-1.1.2 release)
cppflags=''
ccflags =''
stdchar='char', d_stdstdio=undef, usevfork=true
intsize=4, longsize=4, ptrsize=4, doublesize=8
d_longlong=define, longlongsize=8, d_longdbl=define, longdblsize=12
alignbytes=4, usemymalloc=n, prototype=d
