X-Authentication-Warning: delorie.com: mail set sender to geda-help-bounces using -f X-Recipient: geda-help AT delorie DOT com DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=zVFg4IexY7YNXLig4yuq1i0mCAp8H6/k7fx0vX3wpis=; b=CmUM4qJ1OvRj30aADzYQvxFbRpk9r0uH9tcI8zP2XZR7cmvTUuADgptQ1pErJV4xJ7 wYQ74KrfwMOnFP2dlerqEE0R/jxomMkKeFuJl+CnLy1NI7rqLM9z4G+KBopwMMYJtjpt lqZBs1G41lV1f4weYauNKds7tbGl6vwDDRZPKn1yVvE60sVRv92+43ppR641O2SAXA8h htfAg6Eww/0CfPfLYqHpzMiSxNWSTJbD6pVlP2CIm/i4dZIhgbBLbDPMxl675BXZdojw q23Qt6HPC5V7Zr9th76vy3+bEyu6wWw+FljSL8AS35b3O2X3AxZLIppjGG/AC/mhPUQr AYow== MIME-Version: 1.0 X-Received: by 10.180.198.43 with SMTP id iz11mr1211688wic.0.1387431669893; Wed, 18 Dec 2013 21:41:09 -0800 (PST) Date: Thu, 19 Dec 2013 11:11:09 +0530 Message-ID: Subject: [geda-help] PCB segfault on opening specific PCBs From: Shashank Chintalagiri To: geda-help AT delorie DOT com Content-Type: multipart/alternative; boundary=047d7b6250e0d592d404eddc9b2e Reply-To: geda-help AT delorie DOT com --047d7b6250e0d592d404eddc9b2e Content-Type: text/plain; charset=ISO-8859-1 Hi, I've been using PCB without much issue for over a year now. However, all of a sudden, PCB refuses to open a PCB I was working on with a buffer overrun and a segfault. I'm uncertain where / how to look for a solution, so any help or suggestions would be more than welcome. I was working on the PCB earlier without any issue. I exited PCB, made some minor changes to the schematic, and ran gsch2pcb. Subsequent to that, PCB segfaults when opening the PCB. The .pcb.bak generated by that last run of gsch2pcb (as far as I can tell) also causes a segfault, so I think it was something PCB did and not something gsch2pcb did. Older backups, though they are a unfortunately too old for what I would like, seem to be opening fine. I've pasted the full backtrace with memory map which I get at http://pastie.org/8562358 . The relevant portion of the backtrace is as below. $ pcb x-smu.pcb *** buffer overflow detected ***: pcb terminated ======= Backtrace: ========= /lib/x86_64-linux-gnu/libc.so.6(__fortify_fail+0x5c)[0x7fdfb52e808c] /lib/x86_64-linux-gnu/libc.so.6(+0x111020)[0x7fdfb52e7020] /lib/x86_64-linux-gnu/libc.so.6(+0x1104a9)[0x7fdfb52e64a9] /lib/x86_64-linux-gnu/libc.so.6(_IO_default_xsputn+0xdb)[0x7fdfb5252a3b] /lib/x86_64-linux-gnu/libc.so.6(_IO_vfprintf+0x37cf)[0x7fdfb5222f4f] /lib/x86_64-linux-gnu/libc.so.6(__vsprintf_chk+0x94)[0x7fdfb52e6544] /lib/x86_64-linux-gnu/libc.so.6(__sprintf_chk+0x7d)[0x7fdfb52e648d] pcb(CreateNewNet+0x36)[0x446e56] pcb(yyparse+0x3c8f)[0x47536f] pcb[0x470b01] pcb[0x4562c3] pcb(main+0x84b)[0x42653b] /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf5)[0x7fdfb51f7de5] pcb[0x426b49] ======= Memory map: ======== Thanks Shashank -- Chintalagiri Shashank http://blog.chintal.in --047d7b6250e0d592d404eddc9b2e Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Hi,

I've been using PCB wi= thout much issue for over a year now. However, all of a sudden, PCB refuses= to open a PCB I was working on with a buffer overrun and a segfault. I'= ;m uncertain where / how to look for a solution, so any help or suggestions= would be more than welcome.

I was working on the PCB earlier without any issue. I exited PCB,= made some minor changes to the schematic, and ran gsch2pcb. Subsequent to = that, PCB segfaults when opening the PCB. The .pcb.bak generated by that la= st run of gsch2pcb (as far as I can tell) also causes a segfault, so I thin= k it was something PCB did and not something gsch2pcb did. Older backups, t= hough they are a unfortunately too old for what I would like, seem to be op= ening fine.

I've pasted the full backtrace with memory map which I get at= http://pastie.org/8562358 . The = relevant portion of the backtrace is as below.

$ pcb x-smu.pcb
*** buffer overflow detected ***: pcb terminated
=3D=3D=3D=3D=3D=3D=3D B= acktrace: =3D=3D=3D=3D=3D=3D=3D=3D=3D
/lib/x86_64-linux-gnu/libc.so.6(__= fortify_fail+0x5c)[0x7fdfb52e808c]
/lib/x86_64-linux-gnu/libc.so.6(+0x11= 1020)[0x7fdfb52e7020]
/lib/x86_64-linux-gnu/libc.so.6(+0x1104a9)[0x7fdfb= 52e64a9]
/lib/x86_64-linux-gnu/libc.so.6(_IO_default_xsputn+0xdb)[0x7fdfb5252a3b]/lib/x86_64-linux-gnu/libc.so.6(_IO_vfprintf+0x37cf)[0x7fdfb5222f4f]
/l= ib/x86_64-linux-gnu/libc.so.6(__vsprintf_chk+0x94)[0x7fdfb52e6544]
/lib/= x86_64-linux-gnu/libc.so.6(__sprintf_chk+0x7d)[0x7fdfb52e648d]
pcb(CreateNewNet+0x36)[0x446e56]
pcb(yyparse+0x3c8f)[0x47536f]
pcb[0x= 470b01]
pcb[0x4562c3]
pcb(main+0x84b)[0x42653b]
/lib/x86_64-linux-= gnu/libc.so.6(__libc_start_main+0xf5)[0x7fdfb51f7de5]
pcb[0x426b49]
=3D=3D=3D=3D=3D=3D=3D Memory map: =3D=3D=3D=3D=3D=3D=3D=3D

Than= ks
Shashank


--

Chintalagiri Shashank
http://blog.chintal.in

--047d7b6250e0d592d404eddc9b2e--