ALT Linux Sisyphus discussions
 help / color / mirror / Atom feed
From: Vladimir V Kutyavin <vlkut_alt@list.ru>
To: ALT Linux Sisyphus discussions <sisyphus@lists.altlinux.org>,
	 Vitaly Lipatov <lav@altlinux.ru>
Subject: [sisyphus] Экспорт блобов с pxview, stack smashing detected
Date: Fri, 17 Jul 2009 13:34:03 +0500
Message-ID: <4A60377B.10104@list.ru> (raw)

Помогите, пытаюсь достать блобы из базы paradox в отдельные файлы с 
помощью pxview.
$ pxview -v --blobextension=jpg -b Personel.MB Personel.db
datablock position = 2048
. . . . .
datablock position = 1902592
*** stack smashing detected ***: pxview terminated
Аварийный останов

При экспорте без указания расширения или импорте в mysql то же самое. 
Без блобов в mysql импортируется, лишь ругается после каждой записи:
Couldn't get blob data for 1 (2, 3...)

Стоит pxview-0.2.5-alt0.1, ставил из Сизифа pxview-0.2.5-alt1, и libpx 
тоже менял - поведение то же.

В Sysadmins запросили вывод с valgrind:

$valgrind -v pxview Personel.db -b Personel.MB
datablock position = 1886208
datablock position = 2738176
datablock position = 1902592
*** stack smashing detected ***: pxview terminated
==25275==
==25275== Process terminating with default action of signal 6 (SIGABRT)
==25275==    at 0x4129EB6: raise (in /lib/libc-2.5.1.so)
==25275==    by 0x412B660: abort (in /lib/libc-2.5.1.so)
==25275==    by 0x415F52A: (within /lib/libc-2.5.1.so)
==25275==    by 0x41D1D13: __stack_chk_fail (in /lib/libc-2.5.1.so)
==25275==    by 0x4053D83: (within /usr/lib/libpx.so.0.6.3)
==25275==    by 0x404867F: PX_open_blob_fp (in /usr/lib/libpx.so.0.6.3)
==25275==    by 0x404894E: PX_open_blob_file (in /usr/lib/libpx.so.0.6.3)
==25275==    by 0x804BD00: (within /usr/bin/pxview)
==25275==    by 0x41180EB: (below main) (in /lib/libc-2.5.1.so)
==25275==
==25275== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 37 from 1)
--25275--
--25275-- supp:   37 dl-hack3
==25275== malloc/free: in use at exit: 365,392 bytes in 84 blocks.
==25275== malloc/free: 536 allocs, 452 frees, 381,890 bytes allocated.
==25275==
==25275== searching for pointers to 84 not-freed blocks.
==25275== checked 568,628 bytes.
==25275==
==25275== LEAK SUMMARY:
==25275==    definitely lost: 0 bytes in 0 blocks.
==25275==      possibly lost: 0 bytes in 0 blocks.
==25275==    still reachable: 365,392 bytes in 84 blocks.
==25275==         suppressed: 0 bytes in 0 blocks.
==25275== Rerun with --leak-check=full to see details of leaked memory.
--25275--  memcheck: sanity checks: 44 cheap, 2 expensive
--25275--  memcheck: auxmaps: 0 auxmap entries (0k, 0M) in use
--25275--  memcheck: auxmaps: 0 searches, 0 comparisons
--25275--  memcheck: SMs: n_issued      = 29 (464k, 0M)
--25275--  memcheck: SMs: n_deissued    = 0 (0k, 0M)
--25275--  memcheck: SMs: max_noaccess  = 65535 (1048560k, 1023M)
--25275--  memcheck: SMs: max_undefined = 4 (64k, 0M)
--25275--  memcheck: SMs: max_defined   = 80 (1280k, 1M)
--25275--  memcheck: SMs: max_non_DSM   = 29 (464k, 0M)
--25275--  memcheck: max sec V bit nodes:    0 (0k, 0M)
--25275--  memcheck: set_sec_vbits8 calls: 0 (new: 0, updates: 0)
--25275--  memcheck: max shadow mem size:   768k, 0M
--25275-- translate:            fast SP updates identified: 3,485 ( 90.1%)
--25275-- translate:   generic_known SP updates identified: 199 (  5.1%)
--25275-- translate: generic_unknown SP updates identified: 183 (  4.7%)
--25275--     tt/tc: 8,697 tt lookups requiring 8,843 probes
--25275--     tt/tc: 8,697 fast-cache updates, 3 flushes
--25275--  transtab: new        3,300 (68,244 -> 1,141,180; ratio 
167:10) [0 scs]
--25275--  transtab: dumped     0 (0 -> ??)
--25275--  transtab: discarded  6 (164 -> ??)
--25275-- scheduler: 4,488,266 jumps (bb entries).
--25275-- scheduler: 44/50,827 major/minor sched events.
--25275--    sanity: 45 cheap, 2 expensive checks.
--25275--    exectx: 30,011 lists, 132 contexts (avg 0 per list)
--25275--    exectx: 1,025 searches, 893 full compares (871 per 1000)
--25275--    exectx: 0 cmp2, 91 cmp4, 0 cmpAll
Аварийный останов



             reply	other threads:[~2009-07-17  8:34 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-17  8:34 Vladimir V Kutyavin [this message]
2009-07-17  8:43 ` Slava Semushin

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4A60377B.10104@list.ru \
    --to=vlkut_alt@list.ru \
    --cc=lav@altlinux.ru \
    --cc=sisyphus@lists.altlinux.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

ALT Linux Sisyphus discussions

This inbox may be cloned and mirrored by anyone:

	git clone --mirror http://lore.altlinux.org/sisyphus/0 sisyphus/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 sisyphus sisyphus/ http://lore.altlinux.org/sisyphus \
		sisyphus@altlinux.ru sisyphus@altlinux.org sisyphus@lists.altlinux.org sisyphus@lists.altlinux.ru sisyphus@lists.altlinux.com sisyphus@linuxteam.iplabs.ru sisyphus@list.linux-os.ru
	public-inbox-index sisyphus

Example config snippet for mirrors.
Newsgroup available over NNTP:
	nntp://lore.altlinux.org/org.altlinux.lists.sisyphus


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git