Ticket #1149 (closed bug: fixed)
[bug] Segfault in -t trace output
| Reported by: | pmichaud | Owned by: | |
|---|---|---|---|
| Priority: | blocker | Milestone: | |
| Component: | core | Version: | trunk |
| Severity: | high | Keywords: | |
| Cc: | Language: | ||
| Patch status: | Platform: |
Description
While working on debugging some issues in nqp-rx this morning, I ran into a segfault that occurs when running Parrot with the -t option. I've been able to narrow the problem down to this short code snippet (revision 42097):
$ cat z.pir
.sub main
'foo'()
.end
.sub 'foo'
$P0 = getinterp
$P1 = $P0['namespace';1]
say $P1
.end
$ ./parrot z.pir
parrot
$ ./parrot -t1 z.pir
0 set_args PC1
2 set P0, PC9 P0=PMCNULL PC9=Sub=PMC(0x97471dc pc:12)
5 get_results PC1
7 invokecc P0 P0=Sub=PMC(0x97471dc pc:12)
12 getinterp P0 P0=PMCNULL
Segmentation fault
$
When -t causes segfaults on its own, it's much less useful for debugging. :-(
Thanks!
Pm
Change History
Note: See
TracTickets for help on using
tickets.
