Using pads on a 64-bit AMD Athlon compiles and installs fine, but results in core dumps shortly after beeing executed. Who has experienced the same and who knows how to fix it? Any comments or help appreciated.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I haven't heard anyone having problems with a 64-bit Athlon. If you would like to me take a look at it, send me a core dump from a GDB-enabled version of pads. If you can't send it over, no big deal.
The following steps will allow you to compile a GDB enabled pads:
1. Download the pads-1.2.tar.gz source.
2. set the LDFLAGS environment variable. Depending on which shell you're using, execute the following command:
export LDFLAGS="-ggdb"
3. Compile pads: ./configure; make
4. Run pads and wait for it to core dump. Send this core dump to me.
Thanks!
Matt
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I'm using 64 bit Dual Core AMD Opteron(tm) Processor 280 and centos 5 64-bit os.
Compilation of pads went fine and it started running.
With packets on interface, it got segmentation fault.
Has anyone faced this problem before??? Can anyone please help me out???
Thanks in advance.
I have attached the log reports.
----------------------------------------------
[root@localhost pads-1.2]# pads -i eth0
pads - Passive Asset Detection System
v1.2 - 06/17/05
Matt Shelton <matt@mattshelton.com>
[root@localhost pads-1.2]# gdb pads
GNU gdb Red Hat Linux (6.5-16.el5rh)
Copyright (C) 2006 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 "x86_64-redhat-linux-gnu"...Using host libthread_db library
"/lib64/libthread_db.so.1".
(gdb) run
Starting program: /usr/local/bin/pads
pads - Passive Asset Detection System
v1.2 - 06/17/05
Matt Shelton <matt@mattshelton.com>
(gdb) bt
#0 0x0000003f8ae75340 in strlen () from /lib64/libc.so.6
#1 0x0000003f8ae45b78 in vfprintf () from /lib64/libc.so.6
#2 0x0000003f8ae4b778 in fprintf () from /lib64/libc.so.6
#3 0x000000000040b7de in print_asset_screen (rec=0x1f542d60) at output-screen.c:95
#4 0x000000000040b35a in print_asset (ip_addr={s_addr = 4118941706}, port=0, proto=1) at output.c:161
#5 0x0000000000404281 in process_icmp (pkthdr=0x7ffffbc4f2a0, packet=0x1f5390a2 "", len=34, ip_src={s_addr = 4118941706},
ip_dst={s_addr = 270077962}) at packet.c:270
#6 0x0000000000403f72 in process_ip (pkthdr=0x7ffffbc4f2a0, packet=0x1f5390a2 "", len=14) at packet.c:127
#7 0x0000000000403e64 in process_eth (pkthdr=0x7ffffbc4f2a0, packet=0x1f5390a2 "") at packet.c:49
#8 0x0000000000401b2d in process_pkt (args=0x0, pkthdr=0x7ffffbc4f2a0, packet=0x1f5390a2 "") at pads.c:50
#9 0x0000003f8a206ae8 in pcap_open_live () from /usr/lib64/libpcap.so.0.9.4
#10 0x0000003f8a2077f8 in pcap_loop () from /usr/lib64/libpcap.so.0.9.4
#11 0x00000000004021ca in main_pads () at pads.c:279
#12 0x00000000004027d0 in main (argc=1, argv=0x7ffffbc4f4a8) at pads.c:491
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Using pads on a 64-bit AMD Athlon compiles and installs fine, but results in core dumps shortly after beeing executed. Who has experienced the same and who knows how to fix it? Any comments or help appreciated.
Phil,
I haven't heard anyone having problems with a 64-bit Athlon. If you would like to me take a look at it, send me a core dump from a GDB-enabled version of pads. If you can't send it over, no big deal.
The following steps will allow you to compile a GDB enabled pads:
1. Download the pads-1.2.tar.gz source.
2. set the LDFLAGS environment variable. Depending on which shell you're using, execute the following command:
export LDFLAGS="-ggdb"
3. Compile pads: ./configure; make
4. Run pads and wait for it to core dump. Send this core dump to me.
Thanks!
Matt
Hi
I'm using 64 bit Dual Core AMD Opteron(tm) Processor 280 and centos 5 64-bit os.
Compilation of pads went fine and it started running.
With packets on interface, it got segmentation fault.
Has anyone faced this problem before??? Can anyone please help me out???
Thanks in advance.
I have attached the log reports.
----------------------------------------------
[root@localhost pads-1.2]# pads -i eth0
pads - Passive Asset Detection System
v1.2 - 06/17/05
Matt Shelton <matt@mattshelton.com>
[-] Processing Existing assets.csv
[-] Filter: (null)
[-] Listening on interface eth0
Segmentation fault
-------------------------------------------------
[root@localhost pads-1.2]# dmesg
device eth0 entered promiscuous mode
audit(1211448789.509:49): dev=eth0 prom=256 old_prom=0 auid=4294967295
pads[26432]: segfault at 00000000aaadad10 rip 0000003f8ae75340 rsp 00007fffdba058e8 error 4
device eth0 left promiscuous mode
audit(1211448798.293:50): dev=eth0 prom=0 old_prom=256 auid=4294967295
[root@localhost pads-1.2]#
---------------------------------------------------
[root@localhost pads-1.2]# gdb pads
GNU gdb Red Hat Linux (6.5-16.el5rh)
Copyright (C) 2006 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 "x86_64-redhat-linux-gnu"...Using host libthread_db library
"/lib64/libthread_db.so.1".
(gdb) run
Starting program: /usr/local/bin/pads
pads - Passive Asset Detection System
v1.2 - 06/17/05
Matt Shelton <matt@mattshelton.com>
[-] Processing Existing assets.csv
[-] Filter: (null)
[-] Listening on interface eth0
Program received signal SIGSEGV, Segmentation fault.
0x0000003f8ae75340 in strlen () from /lib64/libc.so.6
Thanks,
Aravind
Tested on 32-bit centos5.
It worked.
Do i need to enable any flags for 64 bit compilation???
(gdb) bt
#0 0x0000003f8ae75340 in strlen () from /lib64/libc.so.6
#1 0x0000003f8ae45b78 in vfprintf () from /lib64/libc.so.6
#2 0x0000003f8ae4b778 in fprintf () from /lib64/libc.so.6
#3 0x000000000040b7de in print_asset_screen (rec=0x1f542d60) at output-screen.c:95
#4 0x000000000040b35a in print_asset (ip_addr={s_addr = 4118941706}, port=0, proto=1) at output.c:161
#5 0x0000000000404281 in process_icmp (pkthdr=0x7ffffbc4f2a0, packet=0x1f5390a2 "", len=34, ip_src={s_addr = 4118941706},
ip_dst={s_addr = 270077962}) at packet.c:270
#6 0x0000000000403f72 in process_ip (pkthdr=0x7ffffbc4f2a0, packet=0x1f5390a2 "", len=14) at packet.c:127
#7 0x0000000000403e64 in process_eth (pkthdr=0x7ffffbc4f2a0, packet=0x1f5390a2 "") at packet.c:49
#8 0x0000000000401b2d in process_pkt (args=0x0, pkthdr=0x7ffffbc4f2a0, packet=0x1f5390a2 "") at pads.c:50
#9 0x0000003f8a206ae8 in pcap_open_live () from /usr/lib64/libpcap.so.0.9.4
#10 0x0000003f8a2077f8 in pcap_loop () from /usr/lib64/libpcap.so.0.9.4
#11 0x00000000004021ca in main_pads () at pads.c:279
#12 0x00000000004027d0 in main (argc=1, argv=0x7ffffbc4f4a8) at pads.c:491
On my ubuntu hardy x86_64, I installed valgrind, and pads seems to work, "no segfaults"!
I was trying to debug, and I have no good explanation, but running it under valgrind seems to work!
# sudo aptitude install valgrind
# sudo valgrind ./pads -c /etc/pads/pads.conf
And bob is your uncle!
This is not a solution! Just some info.
Running with --leak-check=full will give one some more info.
It also reports some errors in the code while running.
Edward
I am having this issue on RHEL5/64bit.