Re: LLDB step over command
From: misc@abrakadabra.systems
Subject: LLDB step over command
Date: Wed, 12 May 2021 21:58:31 +0300
> Hello
>
> Im on 6.9 release amd64. Switched to clang and lldb since gcc and gdb are not
> in base anymore. My problem is during debugging for some functions
> command "next/step-over" behaves like "step/step-in".
>
> example code (just for illustration purpose):
> #include
> #include
>
> int main()
> {
> int a = 5, b;
> void *p = malloc(sizeof(int));
> memcpy(p, (void *), sizeof(int));
> b = *(int *)p;
> return b;
> }
>
> compiled with:
> cc -g -Weverything -ansi -pedantic -O0 -o moveint moveint.c
>
> below is the snippet from session where lldb goes into malloc instead of
> step over it.
> ...
> -> 7void *p = malloc(sizeof(int));
> ^
>8memcpy(p, (void *), sizeof(int));
>9b = *(int *)p;
>10 return b;
> (lldb) next
> Process 18050 stopped
> * thread #1, stop reason = step over failed (Could not create return address
> breakpoint. Return address (0x43eae9c89bd) permissions not found.)
> frame #0: 0x043eae9c8ad0 moveint`malloc
> moveint`malloc:
> -> 0x43eae9c8ad0 <+0>: movq 0x11c9(%rip), %r11
> 0x43eae9c8ad7 <+7>: callq 0x43eae9c8a40
> 0x43eae9c8adc <+12>: jmp0x43eae9c8a32
> 0x43eae9c8ae1 <+17>: pushq $0x4
> ...
>
> How should I deal with this?
I have same problem on my OpenBSD 6.9 release amd64 box. However, next
command of lldb is working fine on my OpenBSD 6.9 current amd64 box.
The lldb has been updated to 11.1.0 on OpenBSD current. Can you update
to current your OpenBSD box by
https://cdn.openbsd.org/pub/OpenBSD/snapshots/amd64/?
> Thanks,
> Serge.
>
--
ASOU Masato
Re: 6.9 on VMware Workstation networking issues
I've also tried VMware Workstation 16 Player on Windows10 Pro and the
netowrk is working fine.
--
ASOU Masato
From: Masato Asou
Date: Wed, 12 May 2021 12:51:48 +0900 (JST)
> Hi Moritz,
>
> I upgraded with the following command on my OpenBSD 6.8 release, and
> the network is working fine.
>
> $ doas sysupgrade
>
> I am using ESXi 6.7 and VMware Fusion 12.1.1 and em0 both environment,
> and network is working fine both environment.
>
> Isn't it a VMware Workstation problem?
> Can you try VirtualBox?
> --
> ASOU Masato
>
> From: Moritz Grimm
> Date: Wed, 12 May 2021 00:32:42 +0200
>
>> Hi,
>>
>>
>> Networking has become unusable in all of my virtual installs of 6.9 on
>> VMware Workstation after an (otherwise uneventful) sysupgrade from 6.8
>> to 6.9. They've been working for years and I've upgraded them several
>> times without any issues so far.
>>
>> netstat -ni shows a huge number of Ofail and ping almost always prints
>> and error from sendmsg ("No buffer space available"), but the
>> occasional ping and DNS lookup does go through (at a success rate of
>> <5%). These are the only error messages I am getting.
>>
>> I'm using vmx(4), but also tried em(4) without any success.
>>
>> None of the upgrade69.html configuration changes are applicable, and
>> my pf.conf parses without errors in 6.9.
>>
>> The dmesg output (from version 6.8 below) is almost identical in 6.9,
>> which just shows slightly less memory available.
>>
>> I've run out of debugging ideas and would appreciate some help. My
>> only "solution" right now was to revert to a 6.8 snapshot. I'm also a
>> bit worried that I might run into similar issues on my bare metal
>> installs (which are all "production"), so I haven't tried those, yet.
>>
>>
>> Thanks,
>>
>> -Moritz
>>
>>
>> OpenBSD 6.8 (GENERIC.MP) #5: Mon Feb 22 04:36:10 MST 2021
>>
>> r...@syspatch-68-amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
>> real mem = 519962624 (495MB)
>> avail mem = 489213952 (466MB)
>> random: good seed from bootblocks
>> mpath0 at root
>> scsibus0 at mpath0: 256 targets
>> mainbus0 at root
>> bios0 at mainbus0: SMBIOS rev. 2.7 @ 0xe0010 (620 entries)
>> bios0: vendor Phoenix Technologies LTD version "6.00" date 02/27/2020
>> bios0: VMware, Inc. VMware Virtual Platform
>> acpi0 at bios0: ACPI 4.0
>> acpi0: sleep states S0 S1 S4 S5
>> acpi0: tables DSDT FACP BOOT APIC MCFG SRAT HPET WAET
>> acpi0: wakeup devices PCI0(S3) USB_(S1) P2P0(S3) S1F0(S3) S2F0(S3)
>> S8F0(S3) S16F(S3) S17F(S3) S18F(S3) S22F(S3) S23F(S3) S24F(S3)
>> S25F(S3) PE40(S3) S1F0(S3) PE50(S3) [...]
>> acpitimer0 at acpi0: 3579545 Hz, 24 bits
>> acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
>> cpu0 at mainbus0: apid 0 (boot processor)
>> cpu0: Intel(R) Core(TM) i7-9850H CPU @ 2.60GHz, 2593.36 MHz, 06-9e-0d
>> cpu0:
>> FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,SS,SSE3,PCLMUL,SSSE3,FMA3,CX16,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,HV,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,TSC_ADJUST,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,RDSEED,ADX,SMAP,CLFLUSHOPT,IBRS,IBPB,STIBP,L1DF,SSBD,ARAT,XSAVEOPT,XSAVEC,XSAVES
>> cpu0: 256KB 64b/line 8-way L2 cache
>> cpu0: smt 0, core 0, package 0
>> mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges
>> cpu0: apic clock running at 65MHz
>> cpu1 at mainbus0: apid 2 (application processor)
>> cpu1: Intel(R) Core(TM) i7-9850H CPU @ 2.60GHz, 2593.40 MHz, 06-9e-0d
>> cpu1:
>> FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,SS,SSE3,PCLMUL,SSSE3,FMA3,CX16,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,HV,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,TSC_ADJUST,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,RDSEED,ADX,SMAP,CLFLUSHOPT,IBRS,IBPB,STIBP,L1DF,SSBD,ARAT,XSAVEOPT,XSAVEC,XSAVES
>> cpu1: 256KB 64b/line 8-way L2 cache
>> cpu1: smt 0, core 0, package 2
>> ioapic0 at mainbus0: apid 1 pa 0xfec0, version 20, 24 pins
>> acpimcfg0 at acpi0
>> acpimcfg0: addr 0xf000, bus 0-127
>> acpihpet0 at acpi0: 14318179 Hz
>> acpiprt0 at acpi0: bus 0 (PCI0)
>> acpipci0 at acpi0 PCI0: 0x 0x0011 0x0001
>> acpicmos0 at acpi0
>> "PNP0A05" at acpi0 not configured
>> acpibat0 at acpi0: BAT1 model "VMware Virtual Batt"
>> acpiac0 at acpi0: AC unit online
>> "PNP0A05" at
Re: 6.9 on VMware Workstation networking issues
Hi Moritz,
I upgraded with the following command on my OpenBSD 6.8 release, and
the network is working fine.
$ doas sysupgrade
I am using ESXi 6.7 and VMware Fusion 12.1.1 and em0 both environment,
and network is working fine both environment.
Isn't it a VMware Workstation problem?
Can you try VirtualBox?
--
ASOU Masato
From: Moritz Grimm
Date: Wed, 12 May 2021 00:32:42 +0200
> Hi,
>
>
> Networking has become unusable in all of my virtual installs of 6.9 on
> VMware Workstation after an (otherwise uneventful) sysupgrade from 6.8
> to 6.9. They've been working for years and I've upgraded them several
> times without any issues so far.
>
> netstat -ni shows a huge number of Ofail and ping almost always prints
> and error from sendmsg ("No buffer space available"), but the
> occasional ping and DNS lookup does go through (at a success rate of
> <5%). These are the only error messages I am getting.
>
> I'm using vmx(4), but also tried em(4) without any success.
>
> None of the upgrade69.html configuration changes are applicable, and
> my pf.conf parses without errors in 6.9.
>
> The dmesg output (from version 6.8 below) is almost identical in 6.9,
> which just shows slightly less memory available.
>
> I've run out of debugging ideas and would appreciate some help. My
> only "solution" right now was to revert to a 6.8 snapshot. I'm also a
> bit worried that I might run into similar issues on my bare metal
> installs (which are all "production"), so I haven't tried those, yet.
>
>
> Thanks,
>
> -Moritz
>
>
> OpenBSD 6.8 (GENERIC.MP) #5: Mon Feb 22 04:36:10 MST 2021
>
> r...@syspatch-68-amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
> real mem = 519962624 (495MB)
> avail mem = 489213952 (466MB)
> random: good seed from bootblocks
> mpath0 at root
> scsibus0 at mpath0: 256 targets
> mainbus0 at root
> bios0 at mainbus0: SMBIOS rev. 2.7 @ 0xe0010 (620 entries)
> bios0: vendor Phoenix Technologies LTD version "6.00" date 02/27/2020
> bios0: VMware, Inc. VMware Virtual Platform
> acpi0 at bios0: ACPI 4.0
> acpi0: sleep states S0 S1 S4 S5
> acpi0: tables DSDT FACP BOOT APIC MCFG SRAT HPET WAET
> acpi0: wakeup devices PCI0(S3) USB_(S1) P2P0(S3) S1F0(S3) S2F0(S3)
> S8F0(S3) S16F(S3) S17F(S3) S18F(S3) S22F(S3) S23F(S3) S24F(S3)
> S25F(S3) PE40(S3) S1F0(S3) PE50(S3) [...]
> acpitimer0 at acpi0: 3579545 Hz, 24 bits
> acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
> cpu0 at mainbus0: apid 0 (boot processor)
> cpu0: Intel(R) Core(TM) i7-9850H CPU @ 2.60GHz, 2593.36 MHz, 06-9e-0d
> cpu0:
> FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,SS,SSE3,PCLMUL,SSSE3,FMA3,CX16,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,HV,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,TSC_ADJUST,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,RDSEED,ADX,SMAP,CLFLUSHOPT,IBRS,IBPB,STIBP,L1DF,SSBD,ARAT,XSAVEOPT,XSAVEC,XSAVES
> cpu0: 256KB 64b/line 8-way L2 cache
> cpu0: smt 0, core 0, package 0
> mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges
> cpu0: apic clock running at 65MHz
> cpu1 at mainbus0: apid 2 (application processor)
> cpu1: Intel(R) Core(TM) i7-9850H CPU @ 2.60GHz, 2593.40 MHz, 06-9e-0d
> cpu1:
> FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,SS,SSE3,PCLMUL,SSSE3,FMA3,CX16,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,HV,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,TSC_ADJUST,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,RDSEED,ADX,SMAP,CLFLUSHOPT,IBRS,IBPB,STIBP,L1DF,SSBD,ARAT,XSAVEOPT,XSAVEC,XSAVES
> cpu1: 256KB 64b/line 8-way L2 cache
> cpu1: smt 0, core 0, package 2
> ioapic0 at mainbus0: apid 1 pa 0xfec0, version 20, 24 pins
> acpimcfg0 at acpi0
> acpimcfg0: addr 0xf000, bus 0-127
> acpihpet0 at acpi0: 14318179 Hz
> acpiprt0 at acpi0: bus 0 (PCI0)
> acpipci0 at acpi0 PCI0: 0x 0x0011 0x0001
> acpicmos0 at acpi0
> "PNP0A05" at acpi0 not configured
> acpibat0 at acpi0: BAT1 model "VMware Virtual Batt"
> acpiac0 at acpi0: AC unit online
> "PNP0A05" at acpi0 not configured
> "PNP0A05" at acpi0 not configured
> "PNP0A05" at acpi0 not configured
> "PNP0A05" at acpi0 not configured
> "PNP0A05" at acpi0 not configured
> acpicpu0 at acpi0: C1(@1 halt!)
> acpicpu1 at acpi0: C1(@1 halt!)
> pvbus0 at mainbus0: VMware
> vmt0 at pvbus0
> pci0 at mainbus0 bus 0
> pchb0 at pci0 dev 0 function 0 "Intel 82443BX AGP" rev 0x01
> ppb0 at pci0 dev 1 function 0 "Intel 82443BX AGP" rev 0x01
> pci1 at ppb0 bus 1
> pcib0 at pci0 dev 7 function 0 "Intel 82371AB PIIX4 ISA" rev 0x08
> pciide0 at pci0 dev 7 function 1 "Intel 82371AB IDE" rev 0x01: DMA,
> channel 0 configured to compatibility, channel 1 configured to
> compatibility
> pciide0: channel 0 disabled (no drives)
> pciide0: channel 1 disabled (no drives)
> piixpm0 at pci0 dev 7 function 3 "Intel 82371AB Power" rev 0x08: SMBus
> disabled
> "VMware VMCI" rev 0x10 at pci0 dev 7
Re: Happy Hacking keyboard not working anymore
Hi, From: Norman Golisz Date: Fri, 12 Feb 2021 10:21:05 +0100 > Hi, > > after upgrading to the latest snapshot my keyboard (Happy Hacking > Keyboard) stopped working. I am useing Happy Hacking keyboard model:PD-KB400B and upgraded OpenBSD current by http://ftp.riken.jp/pub/OpenBSD/snapshots/amd64/bsd.rd a few minutes ago. Now, my OpenBSD box works fine and I can use Happy Hacking keyboard. Is your keyboard or USB port broken? > Unfortunately, I can't provide you a dmesg, neither of the previous > (working) snapshot, nor of the current one, due to the lack of a > keyboard. At the very least, I took a picture of my screen displaying > the error messages. > > The last working snapshot has been from 3 to 4 weeks ago. (Sorry, I can't > be more specific than that!) > > Let me know if I can be of help. > > Norman Could you reinstall OpenBSD 6.8 release on your PC? -- ASOU Masato
Re: compiling pmacct on obsd6.8
Hi, From: Salvatore Cuzzilla Date: Mon, 11 Jan 2021 17:40:21 +0100 > I'm having some troubles with compiling the latest version of pmacct > (https://github.com/pmacct/pmacct) on obsd6.8 . > > I just wanted to know if someone was successful with it ... You can use /usr/ports/net/pmacct. -- ASOU Masato
hostctl -q print no infomation
A am using OpenBSD-current on VMware ESXi. The hostinfo command print no information with -q option. Is this a expected behavior? $ hostctl guestinfo.ip 172.19.200.100 $ hostctl -q guestinfo.ip $ The following is an extract from man hostctl. -q Don't ask for confirmation of any default options. -- ASOU Masato
Re: mount dir over another dir
Hi, From: Ono Caritofilaxy Date: Thu, 16 Apr 2020 10:13:51 +0300 > Hello. > > I want to mount /usr/local/srcdir /usr/local/dstdir/subdir > > answer was "no" 3 years ago > https://marc.info/?l=openbsd-misc=149743861203607=2 > > Can I do this now? > If not - why? Is it dangerous? I have no solution about your question. Maybe FUSE (Filesystem in Userspace) can solve your question. SSHFS is useing FUSE. SSHFS can mount remote file system. https://github.com/libfuse/libfuse https://github.com/libfuse/sshfs Oh, I just realized: $ sshfs localhost:/usr/local/srcdir /usr/local/dstdir/subdir How about it? -- ASOU Masato
