PCAP Grabber Not Activating

classic Classic list List threaded Threaded
5 messages Options
Reply | Threaded
Open this post in threaded view
|

PCAP Grabber Not Activating

nomoore
I am using a VLP-16 sensor and need to be able to read in from a .pcap file.
So, I used vcpkg to install PCL with the .pcap feature enabled and found
that most of my #includes were still excluded I then reinstalled pcl without
the pcap feature. At this point, my #includes were all working and
(surprise) the pcap feature wasn't working. I then reinstalled the pcl with
the pcap feature. My #includes were all working but the pcap feature still
isn't working. I can read in from the sensor just fine. I'm pretty sure I'm
using a 32 bit installation on everything. Is that a problem? Do I need to
reinstall everything for a 64 bit architecture? I'm using Windows 10 and
Visual Studio 2017. For simplicity, I'm testing everything with the code
written by unanancyowen, just to give me a benchmark. Once I have that
working, I'll verify my own code is working.

 I've included the first few lines the debugger spit out in case that's
relevant.

'Proj.exe' (Win32): Loaded 'C:\Windows\SysWOW64\ntdll.dll'. Cannot find or
open the PDB file.
'Proj.exe' (Win32): Loaded 'C:\Windows\SysWOW64\kernel32.dll'. Cannot find
or open the PDB file.
'Proj.exe' (Win32): Loaded 'C:\Windows\SysWOW64\KernelBase.dll'. Cannot find
or open the PDB file.
'Proj.exe' (Win32): Loaded 'C:\Windows\SysWOW64\advapi32.dll'. Cannot find
or open the PDB file.
'Proj.exe' (Win32): Loaded 'C:\Windows\SysWOW64\msvcrt.dll'. Cannot find or
open the PDB file.
'Proj.exe' (Win32): Loaded 'C:\Windows\SysWOW64\sechost.dll'. Cannot find or
open the PDB file.
'Proj.exe' (Win32): Loaded 'C:\Windows\SysWOW64\rpcrt4.dll'. Cannot find or
open the PDB file.
'Proj.exe' (Win32): Loaded 'C:\Windows\SysWOW64\sspicli.dll'. Cannot find or
open the PDB file.
'Proj.exe' (Win32): Loaded 'C:\Windows\SysWOW64\cryptbase.dll'. Cannot find
or open the PDB file.
'Proj.exe' (Win32): Loaded 'C:\Windows\SysWOW64\bcryptprimitives.dll'.
Cannot find or open the PDB file.
'Proj.exe' (Win32): Loaded 'C:\Windows\SysWOW64\ws2_32.dll'. Cannot find or
open the PDB file.
'Proj.exe' (Win32): Loaded
'C:\Users\Name\source\repos\Proj\Debug\boost_date_time-vc141-mt-gd-x32-1_66.dll'.
Symbols loaded.
'Proj.exe' (Win32): Loaded
'C:\Users\Name\source\repos\Proj\Debug\boost_system-vc141-mt-gd-x32-1_66.dll'.
Symbols loaded.
'Proj.exe' (Win32): Loaded
'C:\Users\Name\source\repos\Proj\Debug\pcl_common_debug.dll'. Cannot find or
open the PDB file.
'Proj.exe' (Win32): Loaded
'C:\Users\Name\source\repos\Proj\Debug\pcl_io_debug.dll'. Cannot find or
open the PDB file.
'Proj.exe' (Win32): Loaded
'C:\Users\Name\source\repos\Proj\Debug\pcl_visualization_debug.dll'. Cannot
find or open the PDB file.
'Proj.exe' (Win32): Unloaded
'C:\Users\Name\source\repos\Proj\Debug\pcl_io_debug.dll'
'Proj.exe' (Win32): Loaded
'C:\Users\Name\source\repos\Proj\Debug\vtkCommonCore-8.1.dll'. Cannot find
or open the PDB file.

I'm sorry for the lengthy question. I was partly hoping that explaining it
would help me find the problem. The rest of me is hoping more information
will help diagnose my problem. I'm sure there is just something I've
overlooked. I would greatly appreciate anyone pointing out m oversights.

With Gratitude,
Nolan



--
Sent from: http://www.pcl-users.org/
_______________________________________________
[hidden email] / http://pointclouds.org
http://pointclouds.org/mailman/listinfo/pcl-users
Reply | Threaded
Open this post in threaded view
|

Re: PCAP Grabber Not Activating

Sérgio Agostinho

On 22-01-2018 23:09, nomoore wrote:
I am using a VLP-16 sensor and need to be able to read in from a .pcap file.
So, I used vcpkg to install PCL with the .pcap feature enabled and found
that most of my #includes were still excluded I then reinstalled pcl without
the pcap feature. At this point, my #includes were all working and
(surprise) the pcap feature wasn't working. I then reinstalled the pcl with
the pcap feature. My #includes were all working but the pcap feature still
isn't working.
Can you clarify a little bit what do you mean with working/non working includes?

I can read in from the sensor just fine. I'm pretty sure I'm
using a 32 bit installation on everything. Is that a problem? Do I need to
reinstall everything for a 64 bit architecture?
I think the only requirement is to be consistent with your target architecture. All your libs and building targets need to be either 32 or 64 bits. Visual Studio can be of whatever architecture. I'm not fully sure how VS handles some things being debug and others not though.

I'm using Windows 10 and
Visual Studio 2017. For simplicity, I'm testing everything with the code
written by unanancyowen, just to give me a benchmark. Once I have that
working, I'll verify my own code is working.

 I've included the first few lines the debugger spit out in case that's
relevant.

'Proj.exe' (Win32): Loaded 'C:\Windows\SysWOW64\ntdll.dll'. Cannot find or
open the PDB file.
'Proj.exe' (Win32): Loaded 'C:\Windows\SysWOW64\kernel32.dll'. Cannot find
or open the PDB file.
'Proj.exe' (Win32): Loaded 'C:\Windows\SysWOW64\KernelBase.dll'. Cannot find
or open the PDB file.
'Proj.exe' (Win32): Loaded 'C:\Windows\SysWOW64\advapi32.dll'. Cannot find
or open the PDB file.
'Proj.exe' (Win32): Loaded 'C:\Windows\SysWOW64\msvcrt.dll'. Cannot find or
open the PDB file.
'Proj.exe' (Win32): Loaded 'C:\Windows\SysWOW64\sechost.dll'. Cannot find or
open the PDB file.
'Proj.exe' (Win32): Loaded 'C:\Windows\SysWOW64\rpcrt4.dll'. Cannot find or
open the PDB file.
'Proj.exe' (Win32): Loaded 'C:\Windows\SysWOW64\sspicli.dll'. Cannot find or
open the PDB file.
'Proj.exe' (Win32): Loaded 'C:\Windows\SysWOW64\cryptbase.dll'. Cannot find
or open the PDB file.
'Proj.exe' (Win32): Loaded 'C:\Windows\SysWOW64\bcryptprimitives.dll'.
Cannot find or open the PDB file.
'Proj.exe' (Win32): Loaded 'C:\Windows\SysWOW64\ws2_32.dll'. Cannot find or
open the PDB file.
'Proj.exe' (Win32): Loaded
'C:\Users\Name\source\repos\Proj\Debug\boost_date_time-vc141-mt-gd-x32-1_66.dll'.
Symbols loaded.
'Proj.exe' (Win32): Loaded
'C:\Users\Name\source\repos\Proj\Debug\boost_system-vc141-mt-gd-x32-1_66.dll'.
Symbols loaded.
'Proj.exe' (Win32): Loaded
'C:\Users\Name\source\repos\Proj\Debug\pcl_common_debug.dll'. Cannot find or
open the PDB file.
'Proj.exe' (Win32): Loaded
'C:\Users\Name\source\repos\Proj\Debug\pcl_io_debug.dll'. Cannot find or
open the PDB file.
'Proj.exe' (Win32): Loaded
'C:\Users\Name\source\repos\Proj\Debug\pcl_visualization_debug.dll'. Cannot
find or open the PDB file.
'Proj.exe' (Win32): Unloaded
'C:\Users\Name\source\repos\Proj\Debug\pcl_io_debug.dll'
'Proj.exe' (Win32): Loaded
'C:\Users\Name\source\repos\Proj\Debug\vtkCommonCore-8.1.dll'. Cannot find
or open the PDB file.
Most of this log seems fairly harmless except for the line I set to bold, which I'm not sure if it's a problem or not. I haven't seen your code, but I assume on an application which is centered around the grabber, the io module should be required for the entire application lifetime.

So how exactly are things failing for you? Have you tried using a different PCAP file for instance? It might be relevant to use one not captured by you just to be sure.

Cheers


_______________________________________________
[hidden email] / http://pointclouds.org
http://pointclouds.org/mailman/listinfo/pcl-users

signature.asc (836 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: PCAP Grabber Not Activating

nomoore
Thank you for your reply.

By (non)working #includes I mean I would #include a specific file or library
and would get an error because the file couldn't be found or didn't exist.

I figured most of the log was irrelevant, but there is still a lot I don't
know. So I thought it best to include it just in case.

I'll guess the line you bolded is harmless as well considering it is at the
beginning of the log and the visualizer hadn't been initialized yet. (There
are a few thousand more entries after the ones I posted.)

After stepping through the code and checking the states of a few variables I
am finding that grabber->isRunning() is returning false when initialized
with a pcap file, (It returns true when using live data) which leads me to
believe that either something is going wrong with the initialization or it's
somehow failing to accessing the file. Is there anything else that could
prevent the grabber from running?

Thank you for the suggestion to try using other pcap files. I have been
using files that I have captured myself using the VeloView software as well
as files I have downloaded from online.

Thank you for sharing your experience.

Cheers




--
Sent from: http://www.pcl-users.org/
_______________________________________________
[hidden email] / http://pointclouds.org
http://pointclouds.org/mailman/listinfo/pcl-users
Reply | Threaded
Open this post in threaded view
|

Re: PCAP Grabber Not Activating

Sérgio Agostinho
I do find installation problems in PCL modules every now and then, but those are normally the more experimental ones, not the io. This leaves me the impression that you're likely not using cmake to generate your VS project which is something not recommended. 

Can you go through trouble of submitting an issue on the bug tracker with a minimal case showing exactly the grabber not initializing with the pcap file? Please, and I can't stress this enough,  keep the code to a minimal working example. Don't forget to provide a link to one or more pcap files which are failing for you. 

Cheers


_______________________________________________
[hidden email] / http://pointclouds.org
http://pointclouds.org/mailman/listinfo/pcl-users

signature.asc (882 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: PCAP Grabber Not Activating

Stephen McDowell
@nomoore

In case you don’t know how, you generate the visual studio project by requesting that CMake “generator”.  In your console, if you run

$ cmake -G

it will print out the list of available generators.  The visual studio generators are named kind of strangely, but (assuming you are on a 64 bit system), one gotcha you will want to make sure you do is explicitly request the 64 bit version — the default is to use 32 bit builds!  I don’t know why this would affect the installation, but it may.

$ cd path\to\cloned\pcl
$ mkdir build
$ cd build

Now that you have a clean build directory (emphasis: clean, if you already have a build folder, make sure you start from scratch either by deleting it entirely, or using a different folder), it might look like this if you had Visual Studio 2015 installed:

$ cmake -G "Visual Studio 14 2015 Win64" ..

That will generate the .sln project.  You can also use CMake GUI to create this, which may make your life easier.  Either way, once you have the .sln project you can either double click that and build using the Visual Studio UI, or run

$ cmake --build . --config Release

Hope that helps if you are not sure how to use CMake and Visual Studio!


On Feb 2, 2018, at 1:19 AM, Sérgio Agostinho <[hidden email]> wrote:

I do find installation problems in PCL modules every now and then, but those are normally the more experimental ones, not the io. This leaves me the impression that you're likely not using cmake to generate your VS project which is something not recommended. 

Can you go through trouble of submitting an issue on the bug tracker with a minimal case showing exactly the grabber not initializing with the pcap file? Please, and I can't stress this enough,  keep the code to a minimal working example. Don't forget to provide a link to one or more pcap files which are failing for you. 

Cheers

_______________________________________________
[hidden email] / http://pointclouds.org
http://pointclouds.org/mailman/listinfo/pcl-users


_______________________________________________
[hidden email] / http://pointclouds.org
http://pointclouds.org/mailman/listinfo/pcl-users